2020-04-29 Meeting notes

Roll call/

Announcements

@Daniel Michelson

1. ANW-504: As an Archivist, I want to identify an Agent linked to a (Resource | Digital Object | Accession | Resource Component | Digital Object Component) as "Primary"Closed-Complete

2. Note: the following subtasks were associated with this ticket that is already ready for implementation. Should they get passed, closed, or spec’d out? ANW-400: Review and revise EAC import and export for agent recordsClosed-Duplicate ANW-403: EAC-CPF import: support for localDescriptionClosed-Complete

3. ANW-402: EAC-CPF import: support for objectBinWrapClosed-Will Not Do

4. ANW-401: EAC-CPF import: support for objectXmlWrapClosed-Will Not Do

5. ANW-404: Importing EAC-CPF maintenanceHistoryClosed-Complete
   

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.

1. Leave comment that Dev Pri recommends an optional checkbox on the link, and this needs a specification to detail the different combinations (no checks, 1 check, 2 or more checks) and what their outputs are before moving forward. Move to Awaiting More Info.

2-5. Leave as is. Email James.

@Lydia Tang (Unlicensed)

1. ANW-775: As an archivist, I want the Agents and Subject Headings sorted in ResourcesReady for Implementation

2. ANW-503: As an archivist, I want to be able to create top containers independent of specific material description recordsReady for Implementation

3. ANW-955: Respect line break formatting in notes from SI to PUIReady for Implementation

4. ANW-350: Sorting values in enumerations tables is inefficientClosed-Duplicate

5. ANW-868: Enhance sorting capabilities in PUI Container Inventory viewClosed-Will Not Do

1. Usability looked at this and feel it should pass with the cataloger’s comments. Ok?

2. Added a comment requiring barcodes. Can this pass?

3. I think this should pass!

4. Isn’t this a duplicate of the already Ready for Implementation ticket:? Can we just close it?

5. Selfishly, I think this should pass.

1. Leave as is.

2. Ready for Implementation.

3. Leave comment to clarify that this ticket is asking for the ability to create a single line break without having to do tagging. Link to [GUI note interface ticket] as related work. Leave comment and tag Jessica to add How to create a paragraph break and a line break to the user manual. Move to Community Developer.

4. Leave comment that this is a duplicate ticket. Close.

5. Lydia will clarify ticket.

@Edgar Garcia (Unlicensed)

1. ANW-509: As an Archivist, I'd like to be able to create an event type in ASpace without having to also edit the en.yml file.Closed-Will Not Do

2. ANW-622: Public interface converts digital object URI schemes to file: Closed-Will Not Do

3. ANW-861: Approximate, Inferred, and Questionable date Certainty labels need to be reflected in the PUI where dates are listedDevelopment Started

1. I had no trouble creating an event on the test server. Close this ticket.

2. Reporter asked for this ticket to be closed and would open a new ticket when necessary.

3. Certainty labels are not displayed in the PUI. Pass this, but do we know how to display certainty?

1. Comment issue could not be replicated; Close.

2. Close.

3. Comment to add the label in parentheses after the date. Pass.

@Lori Dedeyan (Unlicensed)

From Usability

1. ANW-8: As a repository manager, I want to generate a list of storage units at which my repository stores materialsClosed-Will Not Do

2. https://archivesspace.atlassian.net/browse/ANW-116

3. https://archivesspace.atlassian.net/browse/ANW-117

4. https://archivesspace.atlassian.net/browse/ANW-695

5. https://archivesspace.atlassian.net/browse/ANW-878

6. https://archivesspace.atlassian.net/browse/ANW-100

1. 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.

2. Seems to be basically done (although not exactly) - close?

3. This is covered in this ticket: https://archivesspace.atlassian.net/browse/ANW-923 . Close this one?

4. Usability would like this to pass.

5. Usability would like this to pass with this internal note. Is there currently a way to create a custom repository field?

6. Mostly done. Close?

@Alicia Detelich

1. https://archivesspace.atlassian.net/browse/ANW-974

2. https://archivesspace.atlassian.net/browse/ANW-1015

3. https://archivesspace.atlassian.net/browse/ANW-957

1. Community Developer.

2. Ready for Implementation.

3. Leave comment that needs a specification with possible questions. Awaiting More Information.

@Maggie Hughes

1. https://archivesspace.atlassian.net/browse/ANW-341

2. https://archivesspace.atlassian.net/browse/ANW-755

3. https://archivesspace.atlassian.net/browse/ANW-1007

4. https://archivesspace.atlassian.net/browse/ANW-865

1. 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.

2. coming back to this…

3. 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?

4. Offered to mock up wireframes.

1. Need to tag Jessica Crouch and put in Awaiting More Info. As soon as text is available, it should be passed.

2. close ticket. Comment to please open a new one if the problem persists.

3. Will comment spawning the resource record but feel this is too local of a request.

4. Encourage providing a wireframe. Need clarification on “automatically” - will it require a prompt or automatically do without prompt. If truly automatic, it will negatively impact performance since it would be triggered every time an AO is saved. Might be possibility for a background job? Awaiting More Info.

@Randy Kuehn

1. https://archivesspace.atlassian.net/browse/ANW-171

2. https://archivesspace.atlassian.net/browse/ANW-1013

3. https://archivesspace.atlassian.net/browse/ANW-1012

4. https://archivesspace.atlassian.net/browse/ANW-1021

5. ANW-622: Public interface converts digital object URI schemes to file: Closed-Will Not Do

1. 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

2. 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

3. ANW-1012: Allow local development to restrict access to localhost only
   -Doesn't ArchivesSpace default to localhost only?
   -Recommend: More information?

4. 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

5. 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

1. close

2. skip

3. skip

4. skip

5. close