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
Metadata Standards subcommittee approved - Recommend: move to development
Recommend: local plugin or community development
Summary: Notifications when... a new user profile is created and needs permissions assigned review a completed Assessment end dates for restrictions arrive end dates for copyright arrive I would also like to be able to create customizable reports - Where do we stand on notifications within AS?
Would it be possible to copy relationships? (“changing the relationship from one of subject/resource to agent/resource”) It seems like this type of bulk modification would need an update plugin, no?
This ticket wants the contents of a note preserved when changing the note type (language in the ticket is inconsistent, but this is what they mean). I interpret this as wanting subnotes (specifically text) to remain when changing types. If this is feasible from a development perspective, I recommend passing.
does not need prioritization as ArchivesSpace can already accomplish this first part via “Download Container Labels”. They also ideally want ArchivesSpace to be integrated with the catalog which would need more details in regards to scope and specifications.
does not need prioritization – I could see how they plan to use something like this but not sure how useful it would be for all users of ArchivesSpace. If the consensus is this would be super useful to many then I would vote for prioritization. Miloche suggests using an outside authority control system e.g. LCNAF or SNAC for the master record and adding appropriate information in the ArchivesSpace record to ‘link’ out to these resources i.e. the Record Control Information section.
needs prioritized – enhancing the validator – also there might be a bug / not working as expected – see example in the Jira issue. Additional notes from Miloche: The instructions (/wiki/spaces/ArchivesSpaceUserManual/pages/1173913646) for the container fields says:
the ingester will try to find an already-created Top Container in the database.
If you have defined a barcode:
If there's a match for the barcode for that resource, that Top Container will be used without further checking.Otherwise, a new Top Container will be created.
If you have not defined a barcode:
The type and indicator will be used to search the database for a Top Container that is already associated with the resource;Otherwise, a new Top Container will be created.
Which to me means if there's a Box 1 and Box 2 without a barcode in the record AND a Box 1 and Box 2 with barcodes are in the spreadsheet, new top containers should be added, i.e. the box 1 without a barcode is different from the one with a barcode.
In this scenario, you should be able to add multiple box 1's, each with different barcodes and new containers would be added for each.
So if this isn't how the importer is supposed to work, the instructions need to be updated.
4. Usability discussed this ticket and we wanted to know if this could be a function in the PUI that could be turned off or on. If not we recommend eliminating.