You are viewing an old version of this page. View the current version .
Compare with Current
View Page History
« Previous
Version 14
Next »
Date 25 Jun 2019 1-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
Goals
Take care of old business tickets
Finish reviewing Ready for Implementation tickets from the bug kanban board in terms of suitability for Ready for Community Developer status
Begin reviewing Ready for Implementation tickets from the feature requests kanban board re Ready for Community Developer status
Links Kanban boards:
ArchivesSpace sandbox: http://test.archivesspace.org/
Discussion topics 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
ANW-557
-
Getting issue details...
STATUS
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).
ANW-805
-
Getting issue details...
STATUS
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 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?
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
ANW-616
-
Getting issue details...
STATUS
ANW-215
-
Getting issue details...
STATUS
ANW-453
-
Getting issue details...
STATUS
ANW-468
-
Getting issue details...
STATUS
ANW-332
-
Getting issue details...
STATUS
ANW-340
-
Getting issue details...
STATUS
ANW-534
-
Getting issue details...
STATUS
ANW-528
-
Getting issue details...
STATUS
Edgar
ANW-400
-
Getting issue details...
STATUS
No - Not for Community Developer
This is a high priority touching importing, otherwise should be ready it seems
ANW-386
-
Getting issue details...
STATUS
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.
ANW-330
-
Getting issue details...
STATUS
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.
ANW-540
-
Getting issue details...
STATUS
Yes
ANW-455
-
Getting issue details...
STATUS
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.
ANW-490
-
Getting issue details...
STATUS
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.
ANW-473
-
Getting issue details...
STATUS
No
This is a major priority and might require more information to be completed.
ANW-539
-
Getting issue details...
STATUS
Yes, a Community Developer should be able to work on this task
Should Priority be lowered from Major? To Minor?
Terra
ANW-532
-
Getting issue details...
STATUS
ANW-550
-
Getting issue details...
STATUS
ANW-517
-
Getting issue details...
STATUS
ANW-443
-
Getting issue details...
STATUS
ANW-462
-
Getting issue details...
STATUS
ANW-445
-
Getting issue details...
STATUS
ANW-442
-
Getting issue details...
STATUS
ANW-489
-
Getting issue details...
STATUS
Lydia
ANW-214
-
Getting issue details...
STATUS
no - not for a community developer
is there enough info. What should an unpublished archival object look like?
Priority is ok at low.
ANW-538
-
Getting issue details...
STATUS
no - 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
ANW-349
-
Getting issue details...
STATUS
possibly, but I don’t know if a community developer would know how to do this
a nice usability feature
priority is low and could be trivial instead
ANW-97
-
Getting issue details...
STATUS
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 minor ok
ANW-553
-
Getting issue details...
STATUS
no - not for a community developer, it sounds like the datepicker currently used is part of a larger discussion
a nice usability feature
priority minor ok
ANW-348
-
Getting issue details...
STATUS
no - sounds complex
a nice usability feature
priority minor ok
ANW-559
-
Getting issue details...
STATUS
no - this involves some architecture planning that probably the program team only knows
a nice usability feature
priority minor ok
ANW-564
-
Getting issue details...
STATUS
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.
Patrick
ANW-352
-
Getting issue details...
STATUS
Yes
Just moving the location of the revision statement notes
ANW-207
-
Getting issue details...
STATUS
No
As of Feb. 2018 we said we needed more information about the size/scope of the work
ANW-561
-
Getting issue details...
STATUS
No
Too large of scope and already part of Staff Interface working group specs
ANW-210
-
Getting issue details...
STATUS
Yes
Seems to be just pulling some data into a form.
ANW-384
-
Getting issue details...
STATUS
Yes
However, don’t know how intricate RDE work is.
ANW-329
-
Getting issue details...
STATUS
Yes
Would also need to update Repository preferences to add this as an allowable column
ANW-253
-
Getting issue details...
STATUS
Yes
I think there are some questions about whether this is a unique issue though
ANW-280
-
Getting issue details...
STATUS
Yes
Julia
ANW-255
-
Getting issue details...
STATUS
ANW-256
-
Getting issue details...
STATUS
ANW-277
-
Getting issue details...
STATUS
ANW-273
-
Getting issue details...
STATUS
ANW-615
-
Getting issue details...
STATUS
ANW-601
-
Getting issue details...
STATUS
ANW-638
-
Getting issue details...
STATUS
ANW-658
-
Getting issue details...
STATUS
Alicia
ANW-661
-
Getting issue details...
STATUS
ANW-662
-
Getting issue details...
STATUS
ANW-663
-
Getting issue details...
STATUS
ANW-681
-
Getting issue details...
STATUS
ANW-685
-
Getting issue details...
STATUS
ANW-685
-
Getting issue details...
STATUS
ANW-725
-
Getting issue details...
STATUS
ANW-730
-
Getting issue details...
STATUS
Extras (Lydia took them)
ANW-738
-
Getting issue details...
STATUS
no - too complex for community dev.
worthwhile project - is spec ok?
minor priority seems ok
ANW-759
-
Getting issue details...
STATUS
no - too complex for community dev.
worthwhile project - is spec ok?
minor priority seems ok
ANW-808
-
Getting issue details...
STATUS
unsure if this is still an issue, could possibly close?
ANW-799
-
Getting issue details...
STATUS
no - unsure if community developers would have access to this security area, otherwise seems relatively straightforward to find the right code to fix.
ANW-806
-
Getting issue details...
STATUS
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.
ANW-809
-
Getting issue details...
STATUS
no? not sure how complex it would be to fix
priority of major is good because of accessibility being protected by law.
ANW-816
-
Getting issue details...
STATUS
no? not sure how complex it would be to fix
ANW-843
-
Getting issue details...
STATUS
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
ANW-908
-
Getting issue details...
STATUS
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
Action items
Decisions