Versions Compared

Old Version 1

changes.mady.by.user Lydia Tang

Saved on

compared with

New Version 2

changes.mady.by.user Lydia Tang

Saved on

Key

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

...

Participants

Goals

  • Finish assessing Ready for Implementation tickets for suitability of “Ready for Community Developer” status

  • When assessing, please answer the following questions:

  1. Candidate for Ready for Community Developer? YES/NO (primary concern)

  2. Whether the ticket is still relevant, its priority ranking, and the tags (secondary concerns)

Discussion topics

Item

Who

Notes

Decision

Announcements?


Old business

Terra

  1. ANW-149

    1. yes

    2. yes

    3. not sure/phydesc imported fine for me.

  2. ANW-170

    1. yes

    2. yes

    3. no (works correctly in sandbox). But, I agree about maybe changing date picker, so it doesn’t block ‘date expression’ field.

  3. ANW-365

    1. yes

    2. yes

    3. ask Christine if updated based on other ticket updates.

  4. ANW-369

    1. yes

    2. no? higher priority re: accessibility?

    3. yes


Alicia

  1. ANW-347

    1. y

  2. ANW-234

    1. y

  3. ANW-251

  4. ANW-262

    1. n

  5. ANW-261

    1. n

      1. Same issue as above

Lydia

  1. ANW-323

    1. this is a catchcall catchall for issues on a theme. Most of those issues are resolved and the rest are in ready for implementation. Close this ticket?

  2. ANW-604

    1. seems to be resolved. Close?

  3. ANW-425

    1. no? Perhaps too complex

    2. major priority, major UX/accessibility issue

  4. ANW-635

    1. need to investigate more

  5. ANW-652

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

  6. ANW-664

    1. need to investigate more

  7. ANW-665

    1. maybe? It could be a simple fix, but I’m not sure how complicated it would be.

  8. ANW-691

    1. need to investigate more

William

  1. ANW-616 - As an Archivist, I want to spawn a new Resource Component from an existing AccessionREADY FOR IMPLEMENTATION

  2. ANW-215 - As repository manager, I would like to display extents and dates in the browse screens for accessions, digital objects, and resources.READY FOR IMPLEMENTATION

  3. ANW-453 - As an archivist, I would like an option to parse multi-part collection identifiers on EAD import READY FOR IMPLEMENTATION

  4. ANW-468 - Database support for MSSQL, Oracle, and PostGRESREADY FOR IMPLEMENTATION

  5. ANW-332 - Sort Collections (Resources) on Staff and Public Interface by Identifier #READY FOR IMPLEMENTATION

  6. ANW-340 - Allow facets to be sorted A to Z in the new PUIREADY FOR IMPLEMENTATION

  7. ANW-534 - As a user, I want to directly edit / modify my user account and passwordREADY FOR IMPLEMENTATION

    ANW-528 - As a repository manager, I want to be able to directly edit a translation value in a controlled value through the UI and not by editing an en.yml file in the application's folders.READY FOR IMPLEMENTATION

    1. y/n to community developer?

    2. priority/other comments?

  8. ANW-215

    1. y/n to community developer?

    2. priority/other comments?

  9. ANW-453

    1. y/n to community developer?

    2. priority/other comments?

  10. ANW-468

    1. y/n to community developer?

    2. priority/other comments?

  11. ANW-332

    1. y/n to community developer?

    2. priority/other comments?

  12. ANW-340

    1. y/n to community developer?

    2. priority/other comments?

Edgar

  1. ANW-400 - Review and revise EAC import and export for agent records READY FOR IMPLEMENTATION

    1. No - Not for Community Developer

    2. This is a high priority touching importing, otherwise should be ready it seems

  2. ANW-386 - Provide a CSV importer for resourcesREADY FOR IMPLEMENTATION

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

  3. ANW-330 - Ensure all interfaces comply with WCAG 2.0 AA, and not AAA READY FOR IMPLEMENTATION

    1. No

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

  4. ANW-540 - As a staff user I would like to set default sort preferences when browsingREADY FOR IMPLEMENTATION

    1. Yes

  5. ANW-455 - As a developer, I want to see links to parent schemas on documentation for a given schema.READY FOR IMPLEMENTATION

    1. Yes

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

  6. ANW-490 - Calendar view not helpful for most archival descriptionREADY FOR IMPLEMENTATION

    1. Yes, a Community Developer should be able to implement this

    2. Has a different date picker been selected? More information might be required for a Community Developer to be able to pick this ticket up.

  7. ANW-473 - EAD to PDF exporter needs to be able to have additional fonts addedREADY FOR IMPLEMENTATION

    1. No

    2. This is a major priority and might require more information to be completed.

  8. ANW-539 - As a repository manager, I would like additional key board shortcuts as itemized below.READY FOR IMPLEMENTATION

    1. Yes, a Community Developer should be able to work on this task

      1. Should Priority be lowered from Major? To Minor?

Terra

  1. ANW-532 - As a developer/archivist, I want the option to export resource components as MARCXML READY FOR IMPLEMENTATION

  2. ANW-550 - As a repository manager, I would like to be able to merge one or more container profile records into another container profile record.READY FOR IMPLEMENTATION

  3. ANW-517 - As a user, I would like to expand all and collapse all components of a finding aid in the tree view.READY FOR IMPLEMENTATION

  4. ANW-443 - Add "Container Profile" to the Browse and Create pulldowns in the global navigationREADY FOR IMPLEMENTATION

  5. ANW-462 - As an archivist, I would like to have a way to merge Top Containers on the Manage Top containers screenREADY FOR IMPLEMENTATION

  6. ANW-445 - Add "Update Indicator" to the new Bulk Operations for top containersREADY FOR IMPLEMENTATION

  7. ANW-442 - As an archivist, I would like to be able to specify that one contact information subrecord for an Agent is the most current or preferred contact information.READY FOR IMPLEMENTATION

  8. ANW-489 - Last Modified only updated at parent Resource level; not at component levelREADY FOR IMPLEMENTATION

Lydia

  1. ANW-214 - As an archivist, I want unpublished archival objects to be distinguishable in the navigation treeREADY FOR IMPLEMENTATION

    1. y/n to community developer?

    2. priority/other comments?

  2. ANW-550

    1. y/n to community developer?

    2. priority/other comments?

  3. ANW-517

    1. y/n to community developer?

    2. priority/other comments?

  4. ANW-443

    1. y/n to community developer?

    2. priority/other comments?

  5. ANW-462

    1. y/n to community developer?

    2. priority/other comments?

Lydia

  1. ANW-214

    1. no - not for a community developer

    2. is there enough info. What should an unpublished archival object look like?

    3. Priority is ok at low.

  2. ANW-538 - As an archivist, I would like to be able to transfer more than one component at a timeREADY FOR IMPLEMENTATION

    1. no - not for a community developer - I don’t know if a community developer would know how to do this.

    2. a nice usability feature

    3. priority is low because of existing workarounds

  3. ANW-349 - Drag to reorder controlled value listsREADY FOR IMPLEMENTATION

    1. possibly, but I don’t know if a community developer would know how to do this

    2. a nice usability feature

    3. priority is low and could be trivial instead

  4. ANW-97 - As an admin, I want to identify inactive users so that they either do not appear or can easily be filtered out of the main user view. READY FOR IMPLEMENTATION

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

    2. a nice usability feature

    3. priority minor ok

  5. ANW-553 - As a staff user, I would like to be able to search for YYYY or YYYY-MM dates in advanced searchREADY FOR IMPLEMENTATION

    1. no - not for a community developer, it sounds like the datepicker currently used is part of a larger discussion

    2. a nice usability feature

    3. priority minor ok

  6. ANW-348 - As a user, I want to be able to conduct 'fuzzy' searches that improve discoverability of words with special charactersREADY FOR IMPLEMENTATION

    1. no - sounds complex

    2. a nice usability feature

    3. priority minor ok

  7. ANW-559 - Manage Users and Manage User Access in same place?READY FOR IMPLEMENTATION

    1. no - this involves some architecture planning that probably the program team only knows

    2. a nice usability feature

    3. priority minor ok

  8. ANW-564 - Undo functionREADY FOR IMPLEMENTATION

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

Julia

  1. ANW-255 - As a Researcher, I want to see collection dates in the collection summary on the 2.x PUI search pageREADY FOR IMPLEMENTATION

  2. ANW-256 - As a Researcher and Staff User, I want to see breadcrumb trails with classification groups and subgroups in the PUI and the staff interface at the collection levelREADY FOR IMPLEMENTATION

  3. ANW-277 - As a repository manager, I would like to display a system alert message while the PUI is being re-indexedREADY FOR IMPLEMENTATION

  4. ANW-273 - As an archivist or researcher I would like there to be tooltips in the PUI that explain termininologyREADY FOR IMPLEMENTATION

  5. ANW-615 - Collection Identifier should also display in the file level or lowest level of description in the public user interfaceREADY FOR IMPLEMENTATION

  6. ANW-601 - Tool tip clarification needed for Title field in Digital Object component records in regards to the use of XLink fieldsREADY FOR IMPLEMENTATION

  7. ANW-638 - As an archivist I would like the existing built-in importers and exporters for the application to be implemented with updated mappingsREADY FOR IMPLEMENTATION

  8. ANW-658 - As a repository manager or archivist, I want the listing of Active and Archived Background Jobs to have more useful informationREADY FOR IMPLEMENTATION

    1. y/n to community developer?

    2. priority/other comments?

  9. ANW-256

    1. y/n to community developer?

    2. priority/other comments?

  10. ANW-277

    1. y/n to community developer?

    2. priority/other comments?

  11. ANW-273

    1. y/n to community developer?

    2. priority/other comments?

  12. ANW-615

    1. y/n to community developer?

    2. priority/other comments?

  13. ANW-601

    1. y/n to community developer?

    2. priority/other comments?

  14. ANW-638

    1. y/n to community developer?

    2. priority/other comments?

  15. ANW-658

    1. y/n to community developer?

    2. priority/other comments?

Maggie

  1. ANW-534

    1. y/n to community developer?

    2. priority/other comments?

  2. ANW-528

    1. y/n to community developer?

    2. priority/other comments?

  3. ANW-442

    1. y/n to community developer?

    2. priority/other comments?

  4. ANW-489

    1. y/n to community developer?

    2. priority/other comments?

  5. ANW-445

    1. y/n to community developer?

    2. priority/other comments?

Extras (Lydia took them)

  1. ANW-738 - As An Administrator I'd Like To Be Able To Split Some PermissionsREADY FOR IMPLEMENTATION

    1. no - too complex for community dev.

    2. worthwhile project - is spec ok?

    3. minor priority seems ok

  2. ANW-759 - Ability to customize by repository which component-level fields appear on the "collection organization" tabREADY FOR IMPLEMENTATION

    1. no - too complex for community dev.

    2. worthwhile project - is spec ok?

    3. minor priority seems ok

  3. ANW-808 - OAI Harvester - Do not return a resumptionToken when there is no more data to retrieve.READY FOR IMPLEMENTATION

    1. unsure if this is still an issue, could possibly close?

  4. ANW-799 - As an archivist with admin privilege, I'd like to access the System Information windowREADY FOR IMPLEMENTATION

    1. no - unsure if community developers would have access to this security area, otherwise seems relatively straightforward to find the right code to fix.

  5. ANW-806 - Make default search operator for PUI configurableREADY FOR IMPLEMENTATION

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

  6. ANW-809 - PDF export needs to be accessible for screen readersREADY FOR IMPLEMENTATION

    1. no? not sure how complex it would be to fix

    2. priority of major is good because of accessibility being protected by law.

  7. ANW-816 - Give sys admin or repository manager level of permissions to toggle CUIs as unpublished or publishedREADY FOR IMPLEMENTATION

    1. no? not sure how complex it would be to fix

  8. ANW-843 - Agents merge from browse continued implementation READY FOR IMPLEMENTATION

    1. no? not sure how complex it would be to fix

    2. priority major, not sure it should be minor, but it would be a helpful function

  9. ANW-908 - As an archivist I want to be able to record language of materials information for an accessionREADY FOR IMPLEMENTATION

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

    2. priority minor seems ok

...