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.” | |
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 |
---|
|
| | |
Alicia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-426 |
---|
|
| | |
Alicia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-301 |
---|
|
| | |
Edgar | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-453 |
---|
|
| Rec: Pass with the comments | |
Edgar | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-476 |
---|
|
| Rec: Pass with the comment | |
Edgar | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-493 |
---|
|
| Rec: PassDiscuss and possibly ask for more information | |
Lora/Laney | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-809 |
---|
|
| | |
Lora/Laney | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-730 |
---|
|
| | |
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) | | |
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? | |
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. | |