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.
I was unable to reproduce the error in v2.8.0 on Windows 10 using the directions provided (https://archivesspace.github.io/tech-docs/administration/windows.html). However, the error did occur when not running against MySQL and setting the jetty shutdown parameters Replied to ticket asking for clarification on procedure Update: Others have experienced this issue. I’ll try a few more scenarios. Status: ongoing
Usability recommends to change the default in the config file to display all notes associated with an archival object in the collection organization view; should not display inherited information (display unique information only). Create new ticket to address “additional description” issue (collection overview, archival object view). Is it possible to add this type of preference to repository preferences rather than needing to edit the config file?
Althea Topek will compile a list of notes - will revisit at the next meeting
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.
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.