Item/Who | Tickets | Recommendations | Decisions |
---|
Roll call and announcements | | Laney has left us! 😞 | |
Tickets
| Theme this month: Old Ticket Purge
| Randy needs to go first!
|
|
Daniel Michelson | https://archivesspace.atlassian.net/browse/ANW-504#icft=ANW-504 The following tickets are proposed to go into the metadata standard swim lane (or Community Developer or close?) https://archivesspace.atlassian.net/browse/ANW-513 https://archivesspace.atlassian.net/browse/ANW-479 https://archivesspace.atlassian.net/browse/ANW-481 https://archivesspace.atlassian.net/browse/ANW-478 https://archivesspace.atlassian.net/browse/ANW-472 https://archivesspace.atlassian.net/browse/ANW-412
| We’d rejected a similar request in a previous ticket, but this one has much clearer reasoning. Keep open. I don’t see anything in this ticket that requires review by the Metadata Standards team. It’s a straightforward request for a new feature. Since it’s in reference to a plugin, recommend assigning to community developer. Same as previous, except that I’m not sure there’s enough information for sending to community developer. Change to either ready for community developer or awaiting more information. Same as 3 Same as 3 Not sure about this ticket, there’s no real information in it. What would we be asking Metadata Standards to weigh in on? This should be sent to Metadata Standards to determine whether VRA Core export for digital objects is an appropriate goal (I suspect the answer is no, but I’m not familiar with VRA).
| |
Lydia Tang (Unlicensed) | https://archivesspace.atlassian.net/browse/ANW-357 https://archivesspace.atlassian.net/browse/ANW-7853. https://archivesspace.atlassian.net/browse/ANW-6084. https://archivesspace.atlassian.net/browse/ANW-871 5. https://archivesspace.atlassian.net/browse/ANW-972 6. https://archivesspace.atlassian.net/browse/ANW-3757. https://archivesspace.atlassian.net/browse/ANW-372
| Unanimously positive responses about this ticket after sharing it on the list. However, it would be a lot of work. Maybe put it on the community developer list? Usability looked at this and thinks it looks good with Ed’s final comments. Pass? very old, mostly fixed. close? Pass? Pass close - too niche and old close - too niche and old
| |
Lori Dedeyan (Unlicensed) | 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-32 |
---|
|
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-524 |
---|
|
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-456 |
---|
|
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-439 |
---|
|
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-440 |
---|
|
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-474 |
---|
|
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-626 |
---|
|
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-408 |
---|
|
| 1. 2. 3. Request is clarified in comments, but the ticket has not been updated since 2015. Close? 4. This seems to fit into the larger set of recommendations regarding the user interface. Would recommend closing this specific ticket. 5. Further info/mapping was supplied by Cory Nimer a couple of months ago, in response to DevPri request- pass on? 6. Have not been able to replicate issue but would be curious if others have had it- agree with 2018 DevPri recommendation to solicit input from users. 7. While not as immediate as having location information directly within a resource/ accession, the top container management functionality does do what this request is asking (show all locations associated with a resource/accession). Recommend closing. 8. This ticket and associated tickets have not been worked on for several years. Close? | |
Alicia Detelich | https://archivesspace.atlassian.net/browse/ANW-980 https://archivesspace.atlassian.net/browse/ANW-319 https://archivesspace.atlassian.net/browse/ANW-287
| | |
Edgar Garcia (Unlicensed) | 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-507 |
---|
|
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-417 |
---|
|
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-477 |
---|
|
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-552 |
---|
|
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-444 |
---|
|
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-523 |
---|
|
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-458 |
---|
|
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-544 |
---|
|
| | |
Maggie Hughes | https://archivesspace.atlassian.net/browse/ANW-600 https://archivesspace.atlassian.net/browse/ANW-963 https://archivesspace.atlassian.net/browse/ANW-814
| Tested in v2.7.0 and is no longer an issue. Rec: close. Confirmed that EAD tags for bold text are still not working in PUI. Not sure what the preferred tag is/does it matter – the ticket uses span. <span> is html, <emph> and <title> are EAD. Doesn’t display in PUI:<span class="bold emph"> , <emph render="bold"> , or just <emph> . <title render="italic"> does work, but changing the attribute value to “bold” doesn’t change it. Rec: pass. Comfirmed issue in v2.7.0. Also noticed in MARCXML export that some relator terms export as translated and some as code. Rec: pass.
| |
Randy Kuehn | 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-392 |
---|
|
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-419 |
---|
|
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-447 |
---|
|
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-449 |
---|
|
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-450 |
---|
|
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-467 |
---|
|
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-475 |
---|
|
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-493 |
---|
|
| Lacking activity Need more information Multiple Subtasks (Awaiting Prioritization): ANW-394, ANW-395, ANW-396, ANW-397, ANW-563 Lacking activity Requires recommended mapping Lacking activity Requires recommended mapping Lacking activity Requires recommended mapping Parent Ticket: ANW-638 Lacking activity Requires recommended mapping Parent Ticket: ANW-638 2017 post suggested revised mapping - waiting on comments Lacking activity
| |
Lora Woodford | Best to review purge tickets to assist in making the purge decisions. Several non-purge tickets as well. | | |
Discussion | Any feedback/questions/suggestions on the Leader Guidance doc? Anything else? | | |