2019-03-20 Meeting notes
Date
Mar 20, 20192-3:30 EST
Call-info
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
Participants
@Lydia Tang (Unlicensed)
Alicia Detelich (absent)
Patrick Galligan (absent)
@Lora Woodford
@Christine Di Bella
Julia McGinnis (absent)
William Modrow (absent)
Regrets:
@Laney McGlohon (Unlicensed)
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 topics
Who | Item | Notes | Decision |
|---|---|---|---|
| Announcements/Questions/Old Business? | Move this to Closed? @Lora Woodford | ANW-422 can be closed! |
Laney/Lora | Not sure this is ASpace thing as opposed to a local thing. Laney will follow-up with Blake. Status: Awaiting More Info. | ||
Laney/Lora |
| Will clarify that it's a manual message that can be set and how to engage. Status: Ready for Implementation. | |
Bill |
|
| |
Bill |
|
| |
Bill |
|
| |
Edgar | Can confirm this is still an issue I recommend we pass. | Status: Ready for Implementation. | |
Edgar | I recommend we pass this. | Might need a partner institution to test this with. Edgar and Maggie will bring up during Integrations meeting and Lydia during UAC meeting. And find out what has been done – individual institutions are doing this. Can we find partners to work on this plugin? Could Edgar and NW help out? Status: Awaiting More Info. | |
Edgar | I recommend we continue to wait for more information. I have pinged the submitter on the ticket. | Ticket is old and likely that some issues here have been fixed. Reporter not responsive. “Closing this ticket but please let us know if this issue still persists.” Status: Close. | |
Lydia | Of course, as the submitter of this ticket, I like these ideas - what do you all think? :) | #1: Chevrons sound ok. #2: “Results” sound good, but is in the yaml and easy to customize #3: needs more detail/a decision on how to sort. Also needs more investigation on tech difficulty. Split into separate tickets and revisit. | |
Lydia | [It seems like the ASpace sandbox is slow today] Can replicate. Why is selecting an extent type only allowable? Perhaps this should be updated so that the two of them are required together and update the tooltip to say so? Also, if there is an error in saving, the error message is off the visible screen. It would be helpful if any error message (or at least something indicating that there is an error) is displayed within the screen view. Rec: Pass | Trivial priority. Rec: Ready for Implementation. | |
Lydia | There’s currently a way to sort Collection Management by processing status. CMs could be applied to Accessions, Resources, etc much more specifically, so I think we should CLOSE this ticket. | Functionality is already there. Rec: Close. | |
Alicia |
|
| |
Alicia |
|
| |
Alicia |
|
| |
Maggie | Could not replicate. Is linked to ANW-608 and some comments suggest that there may be a few different but related issues going on with reordering. Q for Lora: Does this ticket have enough info? Should we solicit more feedback from the listserv? Rec: pass (given the thorough descriptions of the issue which specifically mention that it is difficult to replicate.) | More details are how users are seeing it in their specific environments. Very slippery, looking for points of commonality. Maggie will post message to listserv. Status: Ready for Implementation. | |
Maggie | Didn’t get to this one, sorry! Next time |
| |
Maggie | Tested and confirmed – added note to ticket. Q: Do we expect that we should be able to search for a full identifier string using a hyphen between id components? Or period, space, no space? Red: pass, however it seems a decision might need to be made about how to search for multi-part ids (if possible several ways should work as in keyword searching) | Typeahead would expect it to find it whether it has a hyphen, period, space, or no space between components. Status: Ready for Implementation. | |
Terra | Is exporting in EAD in sandbox, but does not show a Note heading on PUI. example: http://test.archivesspace.org/repositories/2/resources/276 Rec: Pass update for PUI issue | Related to ANW-344. Status: Ready for Implementation. | |
Terra | Repository details are there, but not header/footer option. Can this be done locally? Rec: Repository details are on each collection--if header/footer can be added by institution, I recommend closing ticket. | Similar to recent ticket about adding contact link in a page footer. Can be done locally. Status: Close. | |
Terra | Not sure about this one! | Should be able to do this through the API. Add an option on the importer/background jobs to specify under condition under which to break up id strings: “Break up my ids by [insert character].” Status: Ready for Implementation. | |
Julia |
|
| |
Julia |
|
| |
Julia |
|
| |
Patrick | Need more contextual information about what would "look better". Also need clarity on on the "add into the Edit Basic Information the Resource or Accession number and links back to the component". Do they just want links back to the linked resource/accession? |
| |
Patrick |
|
| |
Patrick |
|
|