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? | |
Bill
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-341 |
---|
|
(possibly already done? Lydia) |
|
|
Bill | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-312 |
---|
|
| | |
Bill | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-453 |
---|
|
| | |
Julia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-736 |
---|
|
| | |
Julia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-621 |
---|
|
| | |
Julia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-620 |
---|
|
| | |
Patrick | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-440 |
---|
| (please email the group if you need someone else to take this ticket - I personally wouldn’t be able to check on this. Lydia) | 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 | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-485 |
---|
| (is this decision already made? Lydia) | 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.” | Christine doesn’t think any mapping changes have been made to the Archon tool. Laney concurs that mapping probably hasn’t changed. According to Laney the work’s already been done. Marked as closed
|
Patrick | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-782 |
---|
|
| Confirmed and duplicated. Agree that this is a minor priority and should go forward as a bug. | |
Alicia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-730 |
---|
|
| Rec: pass; implementation seems relatively simple - see JS snippet from local plugin on ticket | Recommends passing Also in Laney’s list, and she thinks it should be configurable. Add an option in the config file to expand it or not Passed
|
Alicia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-426 |
---|
|
| 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 | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-301 |
---|
|
| 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 | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-453 |
---|
|
| Rec: Pass with the comments | Recommends passing based on special characters that are well-documented Lydia asked if it could be configurable, and Lora suggested that would make it more challenging Will share on user list for more information Awaiting More Information
|
Edgar | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-476 |
---|
|
| Rec: Close; versions get added to daogrp | |
Edgar | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-493 |
---|
|
| Rec: Discuss and possibly ask for more information | |
Lora/Laney | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-809 |
---|
|
| Rec: Pass. Note: PDF generation is done differently from the staff and public UIs and I believe this is for both PDF exports. | Laney believes that this should be passed because there’s enough information Pass, Ready for Implementation and there’s enough info in the ticket and comments
|
Lora/Laney | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-730 |
---|
|
| Rec: Pass. Steve has a solution. One question for the group - should it be configurable? | |
Terra | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-478 |
---|
| (Should Dev. Pri. be even handling plug in requests? Lydia) | | Discussing even without Terra Will need to get community input for mapping Lydia Tang (Unlicensed) will share this on the list and see if others are willing to pick this up
|
Terra | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-733 |
---|
|
| | |
Terra | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-230 |
---|
|
| | |
Lydia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-567 |
---|
|
| 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? | RFP didn’t come through with a developer for this work Harvard tried to pick up the container portion of this work, but doesn’t match up with the RFP Lydia Tang (Unlicensed) suggested that we close 567 and redirect to ticket 571 Lydia Tang (Unlicensed) is going to open 571 and move to Ready for Implementation and close 567 as a duplicate
|
Lydia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-785 |
---|
|
| SIEWG recs on this or relating to this. Rec: pass? | |
Lydia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-117 |
---|
|
| 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 | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-749 |
---|
|
| Pass: Confirmed still an issue in test (v2.5.1) and local instance | |
Maggie | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-488 |
---|
|
| 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 | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-300 |
---|
|
| 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. | Patrick Galligan (Unlicensed) suggest that this is a bug and not shouldn’t be a feature request Lora Woodford checked during the meeting and was unable to duplicate on test installation We will revisit this ticket next time
|