Meeting ID: 954 7939 2806 Passcode: 965674 One tap mobile +13126266799,,95479392806#,,,,,,0#,,965674# US (Chicago) +19292056099,,95479392806#,,,,,,0#,,965674# US (New York)
Dial by your location +1 312 626 6799 US (Chicago) +1 929 205 6099 US (New York) +1 301 715 8592 US (Germantown) +1 346 248 7799 US (Houston) +1 669 900 6833 US (San Jose) +1 253 215 8782 US (Tacoma) 877 853 5257 US Toll-free 888 475 4499 US Toll-free Meeting ID: 954 7939 2806 Passcode: 965674 Find your local number: https://lyrasis.zoom.us/u/ahUXQvjfH
This ticket wants to rename “Repository Processing Note” to “Internal Repository Note,” make it indexable, and be able to run reports for repository notes. This would certainly add some functionality, but I’m not sure that this is a high-priority set of changes. I’m unclear how other institutions use this note--at mine, we don’t really use it at all.
This ticket seeks to have a “suppressed” indicator in the record tree in the staff interface. Currently, this is only visible within the resource record when you’ve clicked on a suppressed record (or through search results). This seems like an easy fix to make complex collections more easy to navigate in the staff interface.
This ticket asks for visible deaccession records in the PUI in the same way that accessions can appear. I imagine it would be fairly simple to add a “publish” checkbox to the deaccession part of the accession record? If so, this is worthwhile to consider. I’m not sure that this deserves high priority unless it’s truly simple to accomplish. Most institutions I know using ASpace don’t display their accessions in the PUI; though my institution does, I don’t think I’d want the deaccessions to display.
There should be something in place to deter a brute force attack against the staff interface login. Possibly need more details or just copy something standard in regards to login and locking out or recaptcha.
Has duplicate Jira ticket so there is interest in it. I asked Miloche about this and she suggested an alternative solution which I am not sure I agree with but she suggested to “add a filter option on the Browse results screen for Events. Then the user can filter to records that have "Processing Complete" or "Cataloged", etc. Would also need an option to find all accession records that do not have an Event (these are likely the unprocessed accessions). There really isn't enough room on the browse results sceen to add this type of information.”
+1 from Miloche on this – she said “I totally agree that this is necessary and should be prioritized. Collections are more likely to have materials about a title of a work (hence subject heading), e.g. Shakespeare's Romeo and Juliet than to have the work itself.”
Awaiting more information, we’ll ask Jessica to include in monthly e-mail
Kevin in comments added solution: $e for relator term AND $4 for relator code. Create companion ticket to request that role attribute in EAD2002 has the relator term.
Seems like it would be useful for archivists. Can we use rules from existing sorting functionality or would we need a spec/new standard (NISO?)? Keep priority as major or change to minor?
<daoset> in EAD3 is “An element for binding together two or more links to digital archival objects.” Should be a subtask of or linked to ANW-472. Could have Metadata Standards sub-team weigh in.
Pass
Awaiting more information, needs a spec
Ask Metadata Standards to confirm this the correct approach; add to ANW-472
Recommended testing earlier version of procrun - Awaiting more info Alicia from Yale is testing other procure versions.
Blake can’t replicate the problem on demand. He thinks “that after a certain number of records are added, the sort that builds that facet is failing”. Has anyone experienced a problem with the year facet failing?
Recommendation: Add parent record restriction status (true/false/null) to child record API response.
This is part of the larger question of how much information should be “above the fold” in the PUI. I disagree with the submitter’s view that subjects and related names are more deserving of being above the fold than conditions governing access and use, language of materials, and extent. I recommend closing the ticket or referring it to the Usability Subteam.
This ticket is asking for the ability to restrict search results to components of specified resources. While it is possible to limit a search to a single resource using the sidebar search in the PUI, that capability is not present in the staff interface and doesn’t allow for searching across a subset of collections. Adding an ability to filter by resource to the search results page would seem the most straightforward way to handle this.
Defined lists have the “add item” button at the top of the list, while ordered lists have it at the bottom of the list. The latter is preferable, so I recommend passing this as is.
Close, long lists aren’t good above the fold
Awaiting more information, needs a spec or more details
This ticket is seeking to add deaccession sub records to Digital Objects. This would mirror Resource records which already have this. It seems a logical request but I do wonder if this is already handled by accessions and resource record worflows where deaccessions can already be recorded?
This ticket is seeking classifications to be added to Digital Objects. The ticket was created to identify a means of mapping legacy digital object metadata into ArchivesSpace with their preference being to use classifications rather than convert to subjects. I think we could request further information on why subjects could not be used.
This ticket is seeking a solution to display in linked resources within Agents all resources associated with that agent together with resources linked to any parent or child agents related to the agent being viewed. Comments in the ticket show that this could be cumbersome for some repositories. Options to search for keywords in SUI also might make this unnecessary to take forward for implementation?
List: all “notes” (except “preferred citation”), linked agents, linked subjects, and published external documents
Published, related accessions should display in the PUI as “related unprocessed material” (similar to published related resources as “related collections”)
Needs more information? No comments since 2015; is this still an issue?
@Althea Topek will compile a list of notes - will revisit at the next meeting.