Who | Item | Notes | Decision |
---|
New business | Workflow tweaks | A new kanban board column of “Ready for Community Developer” Please update your “areas of expertise”: Development Prioritization subteam Do we need to define criteria for these statuses? Minor Major Critical Blocker
| “Ready for Community Developer” Priorities: if everything is a high priority than the devs can’t manage resources and expectations well recognizing that not everything can be high priority – is it something that would be great to have or is it critical to have can help program team manage expectations – what can they set aside
As a group when can re-assess the tickets that have already been passed. Ideas on how we can move forward? Maggie and Lydia will come back next month with some ideas on how can move a survey idea forward – reach out if you have additional thoughts! |
Old business | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-671 |
---|
|
| Split into 3 tickets. Which are ok to pass? 1 & 2? | |
Really old business | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-99 |
---|
|
| close this ticket since the order of the click can be considered a feature. | |
Julia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-819 |
---|
|
| | |
Julia
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-536 |
---|
|
|
|
|
Julia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-488 |
---|
|
| | |
Edgar | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-507 |
---|
|
| | |
Edgar | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-524 |
---|
|
| | |
Edgar | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-477 |
---|
|
| | |
Maggie | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-753 |
---|
|
| Need more information in order to replicate and confirm issue. Have others experienced issues with the NOT operator in PUI? Are developers already aware of the problem or does it need more info? Rec: Awaiting more info | |
Maggie | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-362 |
---|
|
| Might need more info on how it would be added to the staff user interface. Not sure how often 670s are used. If this is complicated and unlikely to be frequently used, should it be passed? Rec: ? | |
Maggie | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-415 |
---|
|
| Needs more detail or a specification. Ticket doesn’t really have an “owner” – should we promote on the listserv? Rec: Awaiting more info | |
William | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-450 |
---|
|
| | |
William | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-548 |
---|
|
| | |
William | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-741 |
---|
|
| | |
Alicia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-739 |
---|
|
| | Pass and change to Trivial Auto-generate code is used here and it is complicated, probably not suited for a Community Dev. |
Alicia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-742 |
---|
|
| | |
Alicia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-814 |
---|
|
| | |
Laney/Lora | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-668 |
---|
|
| | |
Laney/Lora | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-320 |
---|
|
| | |
Terra | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-444 |
---|
|
| | |
Terra | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-497 |
---|
|
| | |
Terra | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-548 |
---|
|
| | |
Lydia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-785 |
---|
|
| Selfishly, I would like this to PASS | |
Lydia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-508 |
---|
|
| This ticket is super old, vague, and probably very difficult to manage. LT proposes to CLOSE this ticket. | |
Lydia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-526 |
---|
|
| This ticket is super old, vague, I don’t know that we even do deaccession records (besides an event). LT proposes to CLOSE this ticket. | |
Patrick | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-355 |
---|
|
| Would like community input on the proposed vocabs for use. Also would love to have external identifiers added to certain models. | |
Patrick | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-557 |
---|
|
| Need more contextual information about what would "look better". Also need clarity on on the "add into the Edit Basic Information the Resource or Accession number and links back to the component". Do they just want links back to the linked resource/accession? | |
Patrick | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-805 |
---|
|
| Ideally pass. Not exactly sure what's causing this, but can confirm that this bug appears. From what I can tell by researching <dao> structure standards, xlink attributes are technically not allowed. Would need to speak to development team about the best way to correct this. | |
Patrick | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-504 |
---|
|
| Would support closing this ticket. Additionally, do not fully know what the purpose for this work would be. | |