...
Item | Notes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Announcements? |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Action list |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Julia: Limit RDE:
Archival Objects advancing bug
Physical Storage info in Resource tree?
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:
William: Is this already done? Finding aid status https://archivesspace.atlassian.net/browse/ANW-603 finding aid status (duplicate of earlier ticket?)
Terra: Citation
(Recommend: identifier is still missing--move to ready for implementation?) Pass Biog-Hist out of fold:
Collection Organization:
(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:
Events 2:
Maggie: Error messaging https://archivesspace.atlassian.net/browse/ANW-251 CUIs again
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 See all records created by particular user:
Rec: Pass Edgar: RDE template bug
Recommend: This is no longer a bug and has been resolved. Error now states:
Location logic and navigation:
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 Rec: close ticket. Lydia will make a separate a ticket re: the simple error problem
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
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:
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).
Search terms in context
Scope and Contents heading in PUI:
Box folder item labels:
|
...