Item | Who | Notes | Decision |
---|
Announcements and discussion | | Who is cycling off this year? Thanks for the members who may be cycling off. | | Old business tickets |
|
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-557 |
---|
|
| Patrick | New comments on ticket and on April Dev Pri meeting notes. | Still not enough actionable info. Keep it closed (can reopen later if more info).Later discussions
| User Forum: Ready for Community Developer status Question about how to become a new Community Developer – is there on info on how to get started? |
Old business tickets | | | |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-805557 |
---|
|
| Patrick Decision notes from May: Leave comment asking for a suggestion of what it should look like. | New comments on ticket and on April Dev Pri meeting notes. | Still not enough actionable info. Keep it closed (can reopen later if more info). |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-805 |
---|
|
| Patrick | Decision notes from May: Leave comment asking for a suggestion of what it should look like. Awaiting More Info. If a good answer comes in, then we can pass or close based on that. | Reviewing Ready for Development tickets: Bug kanban boardLora will need more time to read through Nancy’s comment. Bo and Nancy’s are two different tickets but will need to be fixed at the same time. If conflicting audiences, which is the tie breaker? – Lora will leave a comment to ask. Keep in Awaiting More Info until remaining questions are answered. |
| | | |
Reviewing Ready for Development tickets: Bug kanban board (##/58 tickets) | | | |
| Terra | ANW-149 yes yes not sure/phydesc imported fine for me.
ANW-170 yes yes no (works correctly in sandbox). But, I agree about maybe changing date picker, so it doesn’t block ‘date expression’ field.
ANW-365 yes yes ask Christine if updated based on other ticket updates.
ANW-369 yes no? higher priority re: accessibility? yes
| |
| Alicia | ANW-347 y
ANW-234 y
ANW-251
ANW-262 n
ANW-261 n Same issue as above
| |
| Edgar | ANW-694 Yes It still appears that the whole citation generation process has an issue, should the ticket be updated?
ANW-705 No This is stale (a year old) and no update was provided on specifics of where span tags are being problematic. Recommend closing.
ANW-724 No? Priority is set to Major.
ANW-736 Yes The bug might be difficult to find/fix but otherwise should be ok for a Community Developer to attempt it.
ANW-739 Yes
ANW-750 Yes
ANW-751 Yes? Priority is Major but it seems doable.
ANW-752 Yes
ANW-757 Yes Priority is Major but should this be set to Minor?
Maggie
| ANW-758 No – because involves different problems with SUI pdf exports and PUI pdf exports n/a
ANW-760 No – priority is major n/a
ANW-782 Yes? – minor priority and explains changes in code needed
ANW-783 No – major priority and involves search
ANW-784 No? – think this is a “nice to have” and tagged as a bug and minor, but the standards aspect + importer/exporter make me think it might be complicated Overlaps with Patrick’s answer re: ANW-504
ANW-787 Yes? Not sure exactly what this is describing, tabbing through seemed fine, can Laney offer clarification in description?
ANW-792 Yes? – minor bug, however changes needed aren’t described
ANW-823 – this issue is now CLOSED ANW-880 No – might have been a good candidate (especially with Dartmoth plugin) however it looks like work is already being no on it
| William
Lydia | ANW-249 maybe? it sounds as simple as adding “Identifier” to the sort dropdown menu and its resulting action minor priority could be trivial?
ANW-276 probably not - not sure how complex it would be still a major usability issue
ANW-275 probably not - not sure how complex it would be priority major, could be minor, but is an annoying issue
ANW-288 looks like it’s done. close ticket?
ANW-345 already closed. great!
ANW-292 probably not, sounds complicated
ANW-316 not sure didn’t have time to check if this was still an issue but was noted recently
ANW-308 not sure priority major, maybe could be minor?694: yes ANW-705: CLOSE; Edgar will leave comment that not enough specifity to do work ANW-724: yes ANW-736: pull request all ready in – keep as is ANW-739: yes ANW-750: yes ANW-751: pull request all ready in – keep as is; Laney will check that it is resolved ANW-752: yes ANW-757: yes; change priority to Minor
|
| Maggie | ANW-758 No – because involves different problems with SUI pdf exports and PUI pdf exports n/a
ANW-760 No – priority is major n/a
ANW-782 Yes? – minor priority and explains changes in code needed
ANW-783 No – major priority and involves search
ANW-784 No? – think this is a “nice to have” and tagged as a bug and minor, but the standards aspect + importer/exporter make me think it might be complicated Overlaps with Patrick’s answer re: ANW-504
ANW-787 Yes? Not sure exactly what this is describing, tabbing through seemed fine, can Laney offer clarification in description?
ANW-792 Yes? – minor bug, however changes needed aren’t described
ANW-823 – this issue is now CLOSED ANW-880 No – might have been a good candidate (especially with Dartmoth plugin) however it looks like work is already being done on it
| ANW-758: no ANW-760: no ANW-782: yes ANW-783: no ANW-784: no ANW-787: ping Melissa again – is this still an issue? I tried tabbing through and didn’t have any issues. Separate issue: that there is no visual indication of focus for the expand me button. If we close the original ticket than create new ticket for this visual issue. Lydia will check on it, too. ANW-792: not sure this is wrong – OAI will return deleted records (some people search for deleted records this way) what is in the deleted records table. Christine will check the spec. Change to CLOSE. Behaving as intended, but if you want to propose an enhancement create a new ticket. ANW-823 – this issue is now CLOSED ANW-880: work being done so keep as is
|
| William
Lydia | ANW-249 maybe? it sounds as simple as adding “Identifier” to the sort dropdown menu and its resulting action minor priority could be trivial?
ANW-276 probably not - not sure how complex it would be still a major usability issue
ANW-275 probably not - not sure how complex it would be priority major, could be minor, but is an annoying issue
ANW-288 looks like it’s done. close ticket?
ANW-345 already closed. great!
ANW-292 probably not, sounds complicated
ANW-316 not sure didn’t have time to check if this was still an issue but was noted recently
ANW-308 not sure priority major, maybe could be minor?
| ANW-249: yes ANW-276: no ANW-275: no ANW-288: pull request in – keep as is ANW-345: already closed ANW-292: no ANW-316: pull request in – keep as is ANW-308: no
|
| Julia Lydia
| ANW-323 this is a catchcall for issues on a theme. Most of those issues are resolved and the rest are in ready for implementation. Close this ticket?
ANW-604 seems to be resolved. Close?
ANW-425 no? Perhaps too complex major priority, major UX/accessibility issue
ANW-635 need to investigate more
ANW-652 it seems like improvement has been done but that it didn’t help Cory’s particular issue. Should we close this and ask him to file a new ticket?
ANW-664 need to investigate more
ANW-665 maybe? It could be a simple fix, but I’m not sure how complicated it would be.
ANW-691 need to investigate more
| |
| | | |
Reviewing Ready for Development tickets: Feature request kanban board (65 tickets) | | | |
| William | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-616 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-215 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-453 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-468 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-332 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-340 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-534 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-528 |
---|
|
| |
| Edgar | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-400 |
---|
|
No - Not for Community Developer This is a high priority touching importing, otherwise should be ready it seems
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-386 |
---|
|
This one’s a weird one… I would simply say no to Community Developer due to it also being an importer, but I am unsure what direction this issue is headed. aspace-import-excel plugin exists and I believe supports up to the current version, but I am also unsure how well supported the plugin is or will continue to be. This feature should really be in the core code and maintained internally, but if it remains a separate plugin at Harvard, perhaps Community Developers could assist in maintaining it there, if Harvard requires it.
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-330 |
---|
|
No It appears that Mark Custer wanted to have an outside entity review the new PUI before release and provide suggested fixes. Does this make the issue out of scope now? Should a separate audit ticket be created with a plan after the fact since the new PUI is released? This ticket could be reworded and reused but this isn’t work that would be done by devs, it requires some management-like work.
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-540 |
---|
|
Yes
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-455 |
---|
|
Yes This seems like something a Community Developer could modify/investigate/fix. The parent schema is within the source of the generated doc. It might require some investigation into yard.
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-490 |
---|
|
Yes, a Community Developer should be able to implement this Has a different date picker been selected? More information might be required for a Community Developer to be able to pick this ticket up.
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-473 |
---|
|
No This is a major priority and might require more information to be completed.
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-539 |
---|
|
Yes, a Community Developer should be able to work on this task Should Priority be lowered from Major? To Minor?
| |
| Terra | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-532 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-550 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-517 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-443 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-462 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-445 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-442 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-445489 |
---|
|
| |
| Lydia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-442-214 |
---|
|
no - not for a community developer is there enough info. What should an unpublished archival object look like? Priority is ok at low.
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-489 |
---|
|
Lydiano - not for a community developer - I don’t know if a community developer would know how to do this. a nice usability feature priority is low because of existing workarounds
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-214 |
---|
| no - not for possibly, but I don’t know if a community developer is there enough info. What should an unpublished archival object look like? Priority is ok at low. would know how to do this a nice usability feature priority is low and could be trivial instead
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-53897 |
---|
|
no - not for a community developer - I don’t know if a community developer would know how to do this., particularly if it automatically strips permissions (which would be helpful) a nice usability feature priority is low because of existing workaroundsminor ok
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-349 |
---|
| possibly, but I don’t know if a community developer would know how to do thisno - not for a community developer, it sounds like the datepicker currently used is part of a larger discussion a nice usability feature priority is low and could be trivial insteadminor ok
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-97348 |
---|
|
no - not for a community developer - I don’t know if a community developer would know how to do this, particularly if it automatically strips permissions (which would be helpful)sounds complex a nice usability feature priority minor ok
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-553559 |
---|
|
no - not for a community developer, it sounds like the datepicker currently used is part of a larger discussionthis involves some architecture planning that probably the program team only knows a nice usability feature priority minor ok
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-348 |
---|
|
no - sounds complex a nice usability feature priority minor okClose this ticket. This ticket was in response to an older method of reorder. I can’t currently think of another pressing need for an “undo” function.
| |
| Patrick | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-559 |
---|
|
no - this involves some architecture planning that probably the program team only knows a nice usability feature priority minor okYes Just moving the location of the revision statement notes
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-564 |
---|
|
Close this ticket. This ticket was in response to an older method of reorder. I can’t currently think of another pressing need for an “undo” function.
PatrickNo As of Feb. 2018 we said we needed more information about the size/scope of the work
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-352561 |
---|
|
Yes Just moving the location of the revision statement notesNo Too large of scope and already part of Staff Interface working group specs
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-207210 |
---|
|
No As of Feb. 2018 we said we needed more information about the size/scope of the workYes Seems to be just pulling some data into a form.
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-561384 |
---|
|
No - Too large of scope and already part of Staff Interface working group specs
Yes However, don’t know how intricate RDE work is.
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-210329 |
---|
|
YesSeems to be just pulling some data into a form. Would also need to update Repository preferences to add this as an allowable column
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-384253 |
---|
|
YesHowever, don’t know how intricate RDE work is. I think there are some questions about whether this is a unique issue though
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-329 |
---|
|
Yes Would also need to update Repository preferences to add this as an allowable column
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-253 |
---|
|
Yes I think there are some questions about whether this is a unique issue though
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-280 |
---|
| YesYes
| ANW-352: Change to Awaiting More Info; needs more visual/wireframe – what will this look like? Is it a sub-record or will it just look like a sub-record? Lydia looked into this. ANW-207: no ANW-561: no ANW-210: yes ANW-384: yes; Patrick will leave comment not to add a new linking to location (3 modals) ANW-329: yes ANW-253: work being done – keep as is ANW-280: pull request in – keep as is
|
| Julia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-255 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-256 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-277 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-273 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-615 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-601 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-638 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-658 |
---|
|
| |
| Alicia | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-661 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-662 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-663 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-681 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-685 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-685 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-725 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-730 |
---|
|
| |
| Extras (Lydia took them) | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-738 |
---|
|
no - too complex for community dev. worthwhile project - is spec ok? minor priority seems ok
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-759 |
---|
|
no - too complex for community dev. worthwhile project - is spec ok? minor priority seems ok
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-808 |
---|
|
unsure if this is still an issue, could possibly close?
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-799 |
---|
|
no - unsure if community developers would have access to this security area, otherwise seems relatively straightforward to find the right code to fix.
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-806 |
---|
|
maybe? It sounds like an HM plugin for adapting the Staff Interface might be able to be copied to the PUI, but I don’t know if it’s that easy.
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-809 |
---|
|
no? not sure how complex it would be to fix priority of major is good because of accessibility being protected by law.
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-816 |
---|
|
no? not sure how complex it would be to fix
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-843 |
---|
|
no? not sure how complex it would be to fix priority major, not sure it should be minor, but it would be a helpful function
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-908 |
---|
|
maybe? I’m not sure how difficult it would be to copy code from the Resource record template and also map the data when it is spawned into a Resource. priority minor seems ok
| |