Who/What | Tickets | Notes | Decision |
|---|
Roll call/ Announcements | | | |
Daniel Michelson
| https://archivesspace.atlassian.net/browse/ANW-504 Note: the following subtasks were associated with this ticket that is already ready for implementation. Should they get passed, closed, or spec’d out? https://archivesspace.atlassian.net/browse/ANW-400 https://archivesspace.atlassian.net/browse/ANW-403 https://archivesspace.atlassian.net/browse/ANW-402 https://archivesspace.atlassian.net/browse/ANW-401 https://archivesspace.atlassian.net/browse/ANW-404
|
|
|
Lydia Tang (Unlicensed) | https://archivesspace.atlassian.net/browse/ANW-775 https://archivesspace.atlassian.net/browse/ANW-503 https://archivesspace.atlassian.net/browse/ANW-312955 https://archivesspace.atlassian.net/browse/ANW-350 https://archivesspace.atlassian.net/browse/ANW-608868
| Usability looked at this and feel it should pass with the cataloger’s comments. Ok? From last meeting: Add Added a comment to add a limitation that this would require requiring barcodes. Come back to this one!I suggest to pass this revised version. What do others think?Can this pass? I think this should pass! Isn’t this a duplicate of the already Ready for Implementation ticket:? Can we just close it? Close ticket. A new ticket is created for reordering in the staff interface (with changes persisting). The PUI use case doesn’t seem strong. This is a confusing ticket. (Notes from our December meeting: Lydia Tang (Unlicensed) comment to focus only on PUI (not SUI) and that it needs more specification. Lora Woodford comment on what this work might look like (and that it can’t be done with infinite scroll). Lydia Tang (Unlicensed) to draft a ticket to get rid of infinite scroll. Move to Awaiting More Information.)Selfishly, I think this should pass.
| |
Edgar Garcia (Unlicensed) | https://archivesspace.atlassian.net/browse/ANW-509 https://archivesspace.atlassian.net/browse/ANW-622 https://archivesspace.atlassian.net/browse/ANW-861
| I had no trouble creating an event on the test server. Close this ticket. Reporter asked for this ticket to be closed and would open a new ticket when necessary. Certainty labels are not displayed in the PUI. Pass this, but do we know how to display certainty?
| |
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
| Laney’s comment: “Does the current location report or location holding report take care of this ticket?” – Yes I think the current reports take care of this. Usability thinks close it. Seems to be basically done (although not exactly) - close? This is covered in this ticket: https://archivesspace.atlassian.net/browse/ANW-923 . Close this one? Usability would like this to pass. Usability would like this to pass with this internal note. Is there currently a way to create a custom repository field? Mostly done. Close?
| |
Alicia Detelich | https://archivesspace.atlassian.net/browse/ANW-974 https://archivesspace.atlassian.net/browse/ANW-1015 https://archivesspace.atlassian.net/browse/ANW-957
| | |
Maggie Hughes | https://archivesspace.atlassian.net/browse/ANW-755 https://archivesspace.atlassian.net/browse/ANW-1007 https://archivesspace.atlassian.net/browse/ANW-865
| | |
Randy Kuehn | https://archivesspace.atlassian.net/browse/ANW-171 https://archivesspace.atlassian.net/browse/ANW-1013 https://archivesspace.atlassian.net/browse/ANW-1012 https://archivesspace.atlassian.net/browse/ANW-1021 https://archivesspace.atlassian.net/browse/ANW-622
| ANW-171: Boolean true/false display as yes/no
-Embedded demo database (/archivesspace/locales/en.yml): Working - can't replicate (v2.7.1)
-Production MySQL database with plugin (/archivesspace/plugins/local/frontend/locales/en.yml): -Working - can't replicate (v2.7.1)
-Recommend: Close ticket - Problem resolved as of v2.7.1 ANW-1013: Improved homepage URL error message
-Error message received when new resource Home Page URL doesn't begin with "http" or "https"
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
-Doesn't ArchivesSpace default to localhost only?
-Recommend: More information? 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 ANW-622: Public interface converts digital object URI schemes to file:
-Mixed content...Ahhhhhh!
-Reporter is looking for a better way to handle locally and recommended closing
-Depending on resource location, mixed content may be better handled at the server level
-Recommend: Close ticket
| |