1. I had a very long explanation about how this ticket could modified to make it ready for implementing, but at the end I realized it still wasn’t acceptable (to me anyways). Here’s a summary of the issues:
The ticket wants to be able to identify any linked agent as primary. Since there was no explanation of why this feature was requested in the ticket, it’s not clear if there is a use case beyond importing and exporting MARC records without a 1XX field. That use case could be addressed by changing the behavior of the importer and exporter, without changing the underlying data model.
The 2019 discussion in the comments focused on identifying creator agents as primary. This does not address the issue that was (presumably) the reason for the ticket.
I’m not convinced that having agents flagged as primary is the appropriate way to address any of the issues identified in the ticket.
Supporting MARC import and export is important, but I’m leery of changing the underlying data model due to the idiosyncrasies of MARC.
2-5. These relate to the agents module revision that is under development. Recommend leaving as is.
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?
Looked at this last time. New comment clarifies intent. https://archivesspace.atlassian.net/browse/ANW-273 doesn’t seem to include “search help”. Does this need default text for a search help page - usability? Rec: Pass.
coming back to this…
Any previous discussions of this? Didn’t find older tickets. Think adding Notes to Accession recs would need more buy-in. Accession recs do have a general note, but it’s not “mixed content enabled”. How feasible to allow formatting in general note?
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