Versions Compared

Old Version 30

changes.mady.by.user Randy Kuehn

Saved on

compared with

New Version 31

changes.mady.by.user Randy Kuehn

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

12 ET/ 11 CT/10 MT/9 PT

Call-info

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/619789499
Or iPhone one-tap: US: +16468769923 (619789499#) or +16699006833 (619789499#)

Or Telephone：
Dial(for higher quality, dial a number based on your current location):
US: +1 6468769923 or +1 6699006833 or +1 4086380968

Meeting ID: 619 789 499
International numbers available: https://zoom.us/zoomconference?m=lfJNhr4XU-I8p7oRrXXwebNlh57Ti7kq

Participants

Goals

Old tickets view

8-ish tickets

Decide whether to close or keep it open.

Discussion topics

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

  1. 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?)

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

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

  4. https://archivesspace.atlassian.net/browse/ANW-481

  5. https://archivesspace.atlassian.net/browse/ANW-478

  6. https://archivesspace.atlassian.net/browse/ANW-472

  7. https://archivesspace.atlassian.net/browse/ANW-412

  1. We’d rejected a similar request in a previous ticket, but this one has much clearer reasoning. Keep open.

  2. 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.

  3. 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.

  4. Same as 3

  5. Same as 3

  6. Not sure about this ticket, there’s no real information in it. What would we be asking Metadata Standards to weigh in on?

  7. 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)

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

  2. 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

  1. 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?

  2. Usability looked at this and thinks it looks good with Ed’s final comments. Pass?

  3. very old, mostly fixed. close?

  4. Pass?

  5. Pass

  6. close - too niche and old

  7. close - too niche and old

Lori Dedeyan (Unlicensed)

  1. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-32

  2. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-524

  3. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-456

  4. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-439

  5. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-440

  6. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-474

  7. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-626

  8. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-408

  1. No activity since 2016- last comment suggests issue may be resolved. Close?

2. This hasn’t been updated in several years, though issue may still be relevant. Needs more information.

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. 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

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

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

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

Edgar Garcia (Unlicensed)

  1. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-507

  2. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-417

  3. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-477

  4. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-552

  5. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-444

  6. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-523

  7. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-458

  8. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-544

Maggie Hughes

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

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

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

  1. Tested in v2.7.0 and is no longer an issue. Rec: close.

  2. 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.

  3. 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

  1. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-392

  2. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-419

  3. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-447

  4. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-449

  5. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-450

  6. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-467

  7. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-475

  8. Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-493

  1. Lacking activity
    Need more information
    Multiple Subtasks (Awaiting Prioritization): ANW-394, ANW-395, ANW-396, ANW-397, ANW-563

  2. Parent Ticket: ANW-638
    Lacking activity

  3. Requires recommended mapping

  4. Lacking activity
    Requires recommended mapping

  5. Lacking activity
    Requires recommended mapping

  6. Parent Ticket: ANW-638
    Lacking activity
    Requires recommended mapping

  7. Parent Ticket: ANW-638 2017 post suggested revised mapping - waiting on comments

  8. 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?

Action items

  •  

Decisions