...
Who | Item | Notes | Decision | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Announcements/Questions? | Maggie Hughes has agreed to be our co-leader! Do we need to maintain an Annual Work plan? https://archivesspace.atlassian.net/wiki/spaces/AC/pages/260571148/2017-2018+Development+Prioritization+Work+Plan Should this be updated/archived or scrapped? | ||||||||||||
|
(possibly already done? Lydia) | ||||||||||||
Bill |
| ||||||||||||
Bill |
| ||||||||||||
Julia |
| ||||||||||||
Julia |
| ||||||||||||
Julia |
| ||||||||||||
Patrick |
| Waiting on detailed spec for MARC import. Jason Loeffler (Unlicensed) had set he’d take a stab at it. [From Lydia: Jason may not be active any longer on the project. if not, should we solicit the community for volunteer(s) to tackle this? Sue Luftshein and Cory Nimer tend to help out a lot with MARC issues, maybe they could help? | |||||||||||
Patrick |
| Was unable to duplicate due to being a years-old issue with migrating from Archon. “Prioritization sub-team concurs other URL should map to external document sub-record since URL is easily actionable in that point.” | |||||||||||
Patrick |
| Confirmed and duplicated. Agree that this is a minor priority and should go forward as a bug. | |||||||||||
Alicia |
| Rec: pass; implementation seems relatively simple - see JS snippet from local plugin on ticket | |||||||||||
Alicia |
| Rec: awaiting more info/support from community. No new activity or votes on the ticket since Feb. 2018. Search can be tricky to implement (right?) so need confirmation that this is a widely desired feature. | |||||||||||
Alicia |
| Rec: don’t pass. Does not seem like there is enough room for this on the side navigation pane, and physical storage info is already in the collection organization view. | |||||||||||
Edgar |
| Rec: Pass with the comments | |||||||||||
Edgar |
| Rec: Pass with the comment | |||||||||||
Edgar |
| Rec: Discuss and possibly ask for more information | |||||||||||
Lora/Laney |
| Rec: Pass. Note: PDF generation is done differently from the staff and public UIs and I believe this is for both PDF exports. | |||||||||||
Lora/Laney |
| Rec: Pass. Steve has a solution. One question for the group - should it be configurable? | |||||||||||
Terra |
| ||||||||||||
Terra |
| ||||||||||||
Terra |
| ||||||||||||
Lydia |
| Definitely still an issue. SIEWG has specs on it. A member institution was going to fund/contribute code fixing this. What is that project’s status? Rec: pass? | |||||||||||
Lydia |
| SIEWG recs on this or relating to this. Rec: pass? | |||||||||||
Lydia |
| I recommended that it should go to the Reports subteam to become a report. It’s unclear about how the alert should happen. Email someone? Who? Unfortunately, may need to keep it into Awaiting More Info, unless a decision to kick it to Reports is endorsed. | |||||||||||
Maggie |
| Pass: Confirmed still an issue in test (v2.5.1) and local instance | |||||||||||
Maggie |
| Some prior confusion ticket as to whether this work had been done. Can confirm in test (v2.5.1) that it has not been done i.e, Provenance field (Basic Info section) in Accession recs when spawned does not populate Custodial History note in Resource. Rec: Pass. Think this is a logical, uncontroversial mapping, and widely used across institutions. | |||||||||||
Maggie |
| Added comment and screenshots to ticket. Rec: Pass. Agree that Agents as subjects should be clearly expressed, but add notes about how agents-linked-as-subjects do not appear in PUI at all currently. |
...