2018-11-29 Meeting notes

Announcements?

• Next meeting will be on Tuesday, December 18th at 2pm EST

Action list

ANW-539: As a repository manager, I would like additional key board shortcuts as itemized below.Closed-Will Not DoRec: pass, part of SIEWG recs

ANW-803: file_size_bytes should support 64-bit integersClosed-CompleteRec: pass. Simple ticket re: technical necessity.

Jira tickets

Julia: Limit RDE: ANW-522: As an archivist, I'd like a hard limit on all RDE functions to keep me from trying to add ALL THE SIBLING COMPONENTS at onceClosed-Will Not Do

Archival Objects advancing bug ANW-736: Archival object positions not incrementing correctly in some reorder mode movesClosed-Complete

Physical Storage info in Resource tree? ANW-301: Add Physical Storage Information to Collection Organization side navigationClosed-Will Not Do

Alicia: Losing Items when Editing Ordered Lists https://archivesspace.atlassian.net/browse/ANW-635 Rec: confirmed, PASS

Date string https://archivesspace.atlassian.net/browse/ANW-172 Rec: PASS

Search the collection in all views of PUI: ANW-682: As a researcher, I would like to be able to Search the Collection in the Collection Organization tab alsoClosed-CompleteRec: change priority to trivial, Awaiting more information

William: Is this already done?
PUI Values vs Translation https://archivesspace.atlassian.net/browse/ANW-604

Finding aid status https://archivesspace.atlassian.net/browse/ANW-603

finding aid status (duplicate of earlier ticket?) ANW-312: Publishing the Finding Aid status in the PUI should be configurable (yes or no) in the staff interfaceClosed-Complete

Terra: Citation ANW-288: Citation link for archival objects in PUI is missing the identifierClosed-Complete

(Recommend: identifier is still missing--move to ready for implementation?) Pass

Biog-Hist out of fold: ANW-297: Move Biographical / Historical Note from Additional Description Collapsed MenuClosed-CompleteRec: Pass

Collection Organization: ANW-759: Ability to customize by repository which component-level fields appear on the "collection organization" tabClosed-Will Not Do

(Recommend: I agree it would be nice to customize those sections/components as particular institutions deem necessary. Maybe survey more users? Low prioritization) PASS

Events: ANW-358: As application manager, I want to add Events as a subrecord to accession, resource, digital object, and agent recordsReady for Implementation

Events 2: ANW-509: As an Archivist, I'd like to be able to create an event type in ASpace without having to also edit the en.yml file.Closed-Will Not Do

Maggie: Error messaging https://archivesspace.atlassian.net/browse/ANW-251
Rec: Update error messaging for invalid machine actionable dates on Conditions Governing Access and Conditions Governing Use notes to something useful, e.g. "Error: Machine actionable restriction dates must be formatted as YYYY-MM-DD." Consider adding greyed out example text below fields (as found in archival object dates sub-records) that says "YYY-MM-DD only". Pass

CUIs againANW-770: Component Unique Identifier requestsAwaiting More Information

ANW-780: Making the Component Unique Identifier(CUI) more relevant.Closed-Will Not Do
Rec: 1. Give sys admin or repository manager level of permissions to toggle CUIs as unpublished or published (but still default to published - I think?); 2. CUI replace the Material Type column in the Resource tree of the staff view is best (least impacts general appearance in cases when it's not used, etc.), but still unknown where it should display in the PUI and PDF export; 3. Would it be possible to toggle publishing in SUI, PUI, and PDF separately? Any reason to do this?

Maggie will create a new ticket and pass rec #1 above only

Boolean technicality https://archivesspace.atlassian.net/browse/ANW-171
Rec: Unable to confirm myself, but pass with Laney’s notes

See all records created by particular user: ANW-744: As an archivist, I want to view records created/updated by a particular userAwaiting More Information
Rec: Pass

Edgar: RDE template bug https://archivesspace.atlassian.net/browse/ANW-278

Recommend: This is no longer a bug and has been resolved. Error now states:

Date Type - one or more required (or enter a Title)
Title - must not be an empty string (or enter a Date) Rec: Close ticket

Location logic and navigation: https://archivesspace.atlassian.net/browse/ANW-755

Findings: After studying the issue and speaking with an ASpace user locally, it would appear that adding Temporary to the drop down would drastically change how the feature is being used without much return for it. As it stands, it appears that locations flagged as temporary mean that they are temporary locations that will go away as valid locations in the future contradicting “A location itself (the shelf, etc), doesn’t necessarily cease to exist.” Furthermore, the intended use for a top container’s location is to track where it currently is as well as have previous locations it resided to preserve a history of where it has been. The last comment on August 29 by Sue Luftschein mentioned wanting to indicate that the box will eventually be moved again. This could easily be handled by using the notes field by stating that the Current location is temporary and will eventually be moved. I cannot think of a use case that could justify making a major change to this workflow to add Temporary to the drop down. Additionally, there is a reference to

https://archivesspace.atlassian.net/browse/AR-1197 stating that it might not be fixed. Also, when changing Current location to Previous, requirements change as an End Date is now necessary but there is no visual cue it is required.

Recommendation: I say we ask if using the Notes field to designate temporary location as a label and any other pertinent information like the intended permanent location would be enough to satisfy this issue. We may want to also take any other issues described within this ticket and separate them out to new issues.

Decision: close ticket. Lydia will make a separate a ticket re: the simple error problem

See last used identifier https://archivesspace.atlassian.net/browse/ANW-226

Recommendation: This issue as it stands might be better suited as a plugin instead of a core addition.

Rec 2: After a conversation with a colleague, they informed me that it would be much better if search results contained the Identifier as a column. Then it could easily be sorted by Created in descending order, and the identifiers would be exposed from the latest and on. This would also help find the proper entry, particularly for Accessions since there can be multiple entries for the same collection all named similarly prior to becoming a proper resource/EAD.

Rec: Close

Lydia:

https://archivesspace.atlassian.net/browse/ANW-380

Rec: Awaiting More Information. Cory (who was earlier on Dev. Pri.) already scoped out this ticket and it sound like adding adding beginning and end date expressions would help with mapping the data. However, should there be a way to configure this in case an individual repository doesn’t want to add another field for their staff? Because it’s part of aligning with national/international data structure standards, I think this is worth being part of the main code, although I am not sure how many other institutions actually are planning to use this feature (not mine).

https://archivesspace.atlassian.net/browse/ANW-695Rec: Awaiting More Info: Lydia will add note about difficulty in how to accomplish

Search terms in context https://archivesspace.atlassian.net/browse/ANW-363Keep in Awaiting More Info. Lydia will make a note and tag Laney about the potential difficulty of executing the highlights. It’s definitely a desired issue, but needs more specification.

https://archivesspace.atlassian.net/browse/ANW-795

Scope and Contents heading in PUI: https://archivesspace.atlassian.net/browse/ANW-296 Rec: pass because it is such a common terminology in archives and used in archives research instruction.

Box folder item labels: https://archivesspace.atlassian.net/browse/ANW-466Rec: even though I personally would like this feature, I think there are too many complications with potentially mapping it flexibly with the variety of label templates and personal repository preferences. I think it should be a plug in or else spit out some sort of intermediate adaptable file. Close ticket