Date
2pm EST
Call-in
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/619789499
Or iPhone one-tap: US: +16468769923 (619789499#) or +16699006833 (619789499#)
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 6468769923 or +1 6699006833 or +1 4086380968
Meeting ID: 619 789 499
International numbers available: https://zoom.us/zoomconference?m=lfJNhr4XU-I8p7oRrXXwebNlh57Ti7kq
Attendees
tgullings@uttyler.edu Terra Gullings
Goals
Round robin of Jira assignments
Kanban boards: New bug reports: https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=15
New feature requests: https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=16
Link to ArchivesSpace sandbox: http://test.archivesspace.org/
Discussion items
Item | Notes |
---|---|
Announcements? |
|
Action list | - ANW-539Getting issue details... STATUS Rec: pass, part of SIEWG recs - ANW-803Getting issue details... STATUS Rec: pass. Simple ticket re: technical necessity. |
| Julia: Limit RDE: - ANW-522Getting issue details... STATUS Archival Objects advancing bug - ANW-736Getting issue details... STATUS Physical Storage info in Resource tree? - ANW-301Getting issue details... STATUS 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-682Getting issue details... STATUS Rec: change priority to trivial, Awaiting more information William: Is this already done? Finding aid status https://archivesspace.atlassian.net/browse/ANW-603 finding aid status (duplicate of earlier ticket?) - ANW-312Getting issue details... STATUS Terra: Citation - ANW-288Getting issue details... STATUS (Recommend: identifier is still missing--move to ready for implementation?) Pass Biog-Hist out of fold: - ANW-297Getting issue details... STATUS Rec: Pass Collection Organization: - ANW-759Getting issue details... STATUS (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-358Getting issue details... STATUS Events 2: - ANW-509Getting issue details... STATUS Maggie: Error messaging https://archivesspace.atlassian.net/browse/ANW-251 CUIs again - ANW-770Getting issue details... STATUS
-
ANW-780Getting issue details...
STATUS
Maggie will create a new ticket and pass #1 above only Boolean technicality https://archivesspace.atlassian.net/browse/ANW-171 See all records created by particular user:
-
ANW-744Getting issue details...
STATUS
Edgar: RDE template bug - ANW-278Getting issue details... STATUS Recommend: This is no longer a bug and has been resolved. Error now states:
Location logic and navigation: - ANW-755Getting issue details... STATUS 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 - AR-1197Getting issue details... STATUS 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. See last used identifier - ANW-226Getting issue details... STATUS 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: - ANW-380Getting issue details... STATUS 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). - ANW-695Getting issue details... STATUS Rec: Awaiting More Info: Lydia will add note about difficulty in how to accomplish Search terms in context - ANW-363Getting issue details... STATUS Keep 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. - ANW-795Getting issue details... STATUS Scope and Contents heading in PUI: - ANW-296Getting issue details... STATUS Rec: pass because it is such a common terminology in archives and used in archives research instruction. Box folder item labels: - ANW-466Getting issue details... STATUS Rec: 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 |