2019-04-30 Meeting notes
- Lydia Tang (Unlicensed)
- Maggie Hughes
- Patrick Galligan
Date
Apr 30, 20191-2:30pm EST
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
@Lydia Tang (Unlicensed)
@Lora Woodford
@Christine Di Bella
Regrets:
Goals
Round robin of Jira assignments
Kanban boards: New bug reports: https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=15
New feature requests: https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=16
Link to ArchivesSpace sandbox: http://test.archivesspace.org/
Discussion topics
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 Sub-Team Do we need to define criteria for these statuses?
| “Ready for Community Developer”
Priorities:
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 | Split into 3 tickets. Which are ok to pass? 1 & 2? | New tickets: https://archivesspace.atlassian.net/browse/ANW-866: Pass and move to Community Developer | |
Really old business | close this ticket since the order of the click can be considered a feature. | Intentional feature. Close. | |
Julia |
| ||
Julia | |||
Julia |
|
| |
Edgar | ANW-507: As a User, I want to authenticate using CASClosed-Will Not Do |
|
|
Edgar |
|
| |
Edgar |
|
| |
Maggie | 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 | Close. | |
Maggie | 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? Cory’s comment includes specs and will align with Agents work. Rec: Pass? | Pass and move to Community Developer.
| |
Maggie | Needs more detail or a specification. Ticket doesn’t really have an “owner” – should we promote on the listserv? Rec: Awaiting more info | Close ANW-415 and ANW-416, comment that if feel strongly please re-open. | |
William |
|
| |
William |
|
| |
William |
|
| |
Alicia |
| Pass and change to Trivial Auto-generate code is used here and it is complicated, probably not suited for a Community Dev. | |
Alicia |
| Link to ANW-783. Leave comment that closing because it is redundant to ANW-783. | |
Alicia |
| Needs to be better defined. Role and relator are a bit conflated in the ticket. Brings in EAD standards compliance. Adding relator to the import (see code). Comment to ask for more description and clarification. Move to Awaiting More Info. | |
Laney/Lora |
| Comment on:
Close ticket. | |
Laney/Lora |
| Disconnect between EAD2002 and EAD3. Patrick will comment on needing more specifics on action. Lydia will create new label for “standards”, which is how we can track tickets we want a as-yet-forthcoming standards group to weigh in on. Keep in Awaiting More Info. | |
Terra |
|
| |
Terra |
|
| |
Terra |
|
| |
Lydia | Selfishly, I would like this to PASS |
| |
Lydia | This ticket is super old, vague, and probably very difficult to manage. LT proposes to CLOSE this ticket. |
| |
Lydia | 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 | Would like community input on the proposed vocabs for use. Also would love to have external identifiers added to certain models. | Keep in Awaiting more info. Priority change to minor. Lydia going to add labels “seeking community input” and “linked data”. Possible future convo about prioritziing linked data related work. | |
Patrick | 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 | 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 | Would support closing this ticket. Additionally, do not fully know what the purpose for this work would be. |
|