2019-10-30 Meeting notes

Announcements

• Brief discussion of 2019-2020 workplan - any additional feedback?

• Seeking co-chair

• @

@Lydia Tang (Unlicensed)

1. ANW-535: As a repository manager, I want the title / subtitle to be formatted correctly in the PDF export of a resource descriptionClosed-Will Not Do2. 2.

ANW-341: "Search Help" should be provided within the new PUIAwaiting More Information 3.ANW-825: MARCXML export incorrectly includes subfield $0 when a subject-agent has form/time/place subdivisions Closed-Complete

4. ANW-7: Processing PlanClosed-Will Not Do

1. Recommending to close this because it no longer appears to be an issue.

2. recommending to close as a duplicate to ANW-273

3. pass
4. vague and old. This can be too repository-specific. If there’s a community need, it would be great to get a spec and resubmit the ticket. close.

1. Close.

2. Leave open for now, as it is not an exact duplicate of ANW-273.

3. Pass.

4. Close – old ticket and not enough info.
   
   

@Edgar Garcia (Unlicensed)

1. ANW-696: PUI search/browse fails if returned records contain embedded tagsClosed-Will Not Do

2. ANW-733: PUI container inventory search page: pagination links don't work with facetsClosed-Complete

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

1. could not successfully test properly

2. could not test properly

3. pass

1. @Lora Woodford will follow up. Awaiting more info

2. @Edgar Garcia (Unlicensed) will comment for follow up and clarification with reporter. Awaiting more info

3. pass, Edgar will comment about need for final resolution decision.

@Maggie Hughes

1. ANW-424: Classification descriptions should allow paragraph breaksClosed-Complete

2. ANW-161: User Edit Permissions Spill Over To Other RepositoriesClosed-Will Not Do

3. ANW-935: As head archivist, I want the ability to have two or more processing archivists simultaneously adding Resource Component records using different default resource component values.Closed-Will Not Do

1. Confirmed in v2.6.0. Text box for descriptions allows and holds paragraph breaks in edit mode but view mode only shows raw, not formatted, text.

Rec: pass.

2. Not able to replicate in v2.6.0. A user was was repo manager in one repository was not able to edit the repository preferences in a second repo. Had no access to Global preferences. Has anyone else heard of this issue coming up recently?

Rec: close.

3. Recommend using RDE and saving/naming templates for different users.

Rec: close.

1. Maggie will comment re: the difference between edit mode and view mode. Needs a ticket for notes, maybe @Lydia Tang (Unlicensed) can do this? Pass

2. close

3. @Maggie Hughes will comment to clarify re: RDE and close ticket

@Lori Dedeyan (Unlicensed)

1. ANW-833: In PUI, collection organization tree jumps to bottom when width is adjustedClosed-Complete

2. ANW-873: Multi-part note content does not obey publish setting when using RDEClosed-Complete

3. ANW-869: Unpublished Agents (publish false) should not be included in staff side PDFClosed-Duplicate

1. This seems like a browser issue.

2. Recommend moving forward with development.

3. Have not been able to replicate this issue and suspect that they are not unchecking ‘include unpublished’ button. Waiting for response- likely pass.

2.

3.

@Randy Kuehn

1. ANW-941: Include public url of resource in ead / marcxml exportClosed-Complete

2. ANW-834: PUI side should include an option for a sitemap.xml fileDevelopment Started

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

1. Adequate options provided via “Finding Aid Data” → “EAD Location“ or plugin. Recommend closing ticket.

2.Dynamically generated sitemaps would certainly help with SEO. Recommend moving forward with development including customization options.

3. I’m not sure about the priority on this one, but I think would be a helpful upgrade.

1. Ready for Community developer, comment this as a plug in

2. is this in the scope of ArchivesSpace? This would help boost search results. It should be developed but perhaps there are too many institution-specific variables. Ready for Community Developer as plug in

3. Discussion about if this could be a if-then setting. So, if there’s an existing Biog-hist in the resource record, than it would override viewing the Biog-Hist associated with the agent record. Pass with comments from @Randy Kuehn

Additional thoughts for Randy’s comments: what should it be labeled if there are multiple notes? Especially, what if there are multiple creators? What headings?

@Daniel Michelson

1. https://archivesspace.atlassian.net/browse/ANW-921 2. https://archivesspace.atlassian.net/browse/ANW-912 3. https://archivesspace.atlassian.net/browse/ANW-821

1. This has been discussed at length on the listserv. To summarize, it is currently impossible to create a finding aid with a DACS-compliant preferred citation due to the addition of the url of the finding aid page and the date accessed in the citation function. Recommend passing this on for community developer. If there is a desire to have a function for generating a citation for the finding aid itself, that can be introduced as a separate ticket.

2. Pass

3. There’s a lot of different issues involving restrictions here and it’s not entirely clear whether the restrictions referred to include use restrictions or only access restrictions. I consider this an epic, but I’m not sure how such tickets are handled.

1. Pass; @Edgar Garcia (Unlicensed) will work on a new ticket with long-term solution.

2. Pass.

3. Awaiting more information. @Daniel Michelson leave comment asking for more detail (ex, what are you referring to with “restricted items?”) and should get broken up into multiple tickets.

@Alicia Detelich

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

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

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

1.

2.

3.

1.

2.

3.

@Laney McGlohon (Unlicensed)

@Lora Woodford

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

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

1. Asking someone who does Archon migrations (Brian Harrington) for input.

2. I was able to run the backup script and create a Solr snapshot with version 2.7.0, so suggest closing this ticket as “Will Not Do”

1. Laney reached out to contact for feedback; waiting to hear back.

2. Close.