Who/What | Tickets | Notes | Decision |
|---|
Roll call/ Announcements | | | |
Lori Dedeyan (Unlicensed)
| From Usability https://archivesspace.atlassian.net/browse/ANW-8 https://archivesspace.atlassian.net/browse/ANW-116 https://archivesspace.atlassian.net/browse/ANW-117 https://archivesspace.atlassian.net/browse/ANW-695 https://archivesspace.atlassian.net/browse/ANW-878 https://archivesspace.atlassian.net/browse/ANW-100
|
1. Addressed in Locations Report. No movement on ticket since 2017. Close.
2. No movement on this ticket since 2017. Was looked at by reports subteam but no action. 3. This is covered in this ticket: https://archivesspace.atlassian.net/browse/ANW-923 . Close this one? 4. Facets of this can be drawn out with existing reports (such as Shelflist Report and Resources & Instances), though it would be more useful to be able to export a CSV directly from the collection results, rather than across all collections. Usability would like this to pass. *Note: Available ‘Download CSV’ options draw across all records of a certain type (Location, Container Profile, etc.) without specificity, so I wonder how feasible a selective Top Container CSV download could be. 5. Usability would like this to pass with this internal note. Is there currently a way to create a custom repository field? 6. Addressed and reporter recommends closing. |
|
Randy Kuehn | https://archivesspace.atlassian.net/browse/ANW-1013 https://archivesspace.atlassian.net/browse/ANW-1012 https://archivesspace.atlassian.net/browse/ANW-1021
| ANW-1013: Improved homepage URL error message Recommendation #1: add format note to fields such as Home Page URL and Branding Image URL
Recommendation #2: evaluate validation error messages - modify to include user-friendly message such as "wrong format" followed by specifics like "Did not match regular expression \Ahttps?://[\S]+\z"
Priority: Low ANW-1012: Allow local development to restrict access to localhost only ANW-1021: Generate PDF should not automatically "include unpublished" Confirmed change between v2.5.1 and 2.7.1 Unsure of the reasoning behind the change - perhaps to match EAD & MARCXML export defaults Agree with reporter's reasoning Recommend: Push - set "Include unpublished" default to unchecked (Resource: Export->Generate PDF->Include unpublished) and/or add option for users to set export preferences for EAD, MARCXML, and PDF
| |
Edgar Garcia (Unlicensed) | https://archivesspace.atlassian.net/browse/ANW-1025 https://archivesspace.atlassian.net/browse/ANW-1026 https://archivesspace.atlassian.net/browse/ANW-1027 https://archivesspace.atlassian.net/browse/ANW-1060
| | |
Daniel Michelson | https://archivesspace.atlassian.net/browse/ANW-949 https://archivesspace.atlassian.net/browse/ANW-1035 https://archivesspace.atlassian.net/browse/ANW-817
|
This seems like a good candidate for a plugin. It is currently possible to print an accession record, it’s just ugly and spread across more pages than necessary. The use case for this is specific to the filing habits and internal reporting structure of individual people and institutions. Context/Disclaimer: Maureen (who I work with) originally drafted a ticket that combined ANW-950 and this issue. She asked me to review it and I suggested breaking into two, since I didn’t (and don’t) think the accession print option is nearly as important as the PUI one.
2. Making citation information compatible with citation software certainly seems like a useful addition and I recommend moving to ready for implementation, provided there is enough information in the ticket for the developer. 3. This ticket was submitted by Blake on our behalf as part of our data remediation after migration to ArchivesSpace. The title is a little misleading, since controlled value field problems were the cause of the specific problem we encountered, which is unrelated to the requested feature. Mark Cooper was able to force a regeneration in our specific situation, but this would be helpful to have as a background job for the benefit of those with limited technical support. I suggest changing to ready for implementation, but reducing priority to trivial.
| |
Maggie Hughes | https://archivesspace.atlassian.net/browse/ANW-21 https://archivesspace.atlassian.net/browse/ANW-8 https://archivesspace.atlassian.net/browse/ANW-511 https://archivesspace.atlassian.net/browse/ANW-536
| | |
Alicia Detelich | https://archivesspace.atlassian.net/browse/ANW-158 https://archivesspace.atlassian.net/browse/ANW-554 https://archivesspace.atlassian.net/browse/ANW-498
| | |
Lydia Tang (Unlicensed) | https://archivesspace.atlassian.net/browse/ANW-729 https://archivesspace.atlassian.net/browse/ANW-744 https://archivesspace.atlassian.net/browse/ANW-1000
| User scenario: as a repository manager, I would like to see what has been created or updated in a given timeframe, perhaps as a CSV export?
2. This ticket has a lot of viewers (5). Selfishly, I would like this ticket to pass. I don’t think the community really engages in the Jira system, so we haven’t received any interaction on this ticket, besides these watchers, but I do think that this is getting at a desire to be able to compile records created or updated by a certain person. I’m not sure how it would work if a record is updated by someone else (if it would also stop showing up as “stats” for the earlier person, for example). 3. Selfishly, I would like this to pass, but I don’t know how this would work with multiple languages. | |