/
Community Priorities Dashboard Development

Community Priorities Dashboard Development

 

Development Plan

  1. Gather all SIG priorities

  2. Review top 5s together on PC Slack and in PC meeting on 4/24

  3. Draft prototype community priorities dashboard Jira, review as a group, and determine how to come up with a single rank PC list (5/8) << We are here

  4. Refine further, prepare for wider distribution (target 5/16)

  5. Share for feedback at June SIG Conveners meeting, POs, PC, and TC.

  6. Pilot publishing to community in July, determine plan for maintenance & distribution

  7. Publicize and get feedback at WOLFCon

Iteration 1: Top 5s

Group

Priority #1

Priority #2

Priority #3

Priority #4

Priority #5

Group

Priority #1

Priority #2

Priority #3

Priority #4

Priority #5

Acquisitions

UXPROD-4589: Submit Orders via automated email integrationDraft

UXPROD-4243: Enable staff to change default Loan Type value for item when creating a PO LineDraft

UIREC-273: Receipt status for withdrawn itemsOpen

UIOR-1190: Display Vendor Invoice Number in place of FOLIO invoice ID in related invoicesOpen

UIF-480: Export transaction list from FinanceOpen

Cross App

UXPROD-4547: Search across FOLIO apps should be case insensitiveDraft

https://folio-org.atlassian.net/browse/UXPROD-4546

https://folio-org.atlassian.net/browse/UXPROD-4545

https://folio-org.atlassian.net/browse/STCOM-1160

UXPROD-1647: Theme: Ability to maintain relationships between other apps when holdings/items are movedOpen

ERM

UXPROD-5188: Agreements: Implement RBAC based access to resourcesOpen

UXPROD-5193: Agreements Local KB: Remote KB search integrationOpen

UXPROD-5189: Agreements Local KB: Delete packages / delete package contentOpen

UXPROD-5256: ERM: Improvements to publicLookup APIOpen

 

Discovery

UXPROD-4805 - Bulk renewals

Tell the Discovery system what item is holdable

Tell the Discovery system what item is renewable

Ability to Sort Items in FOLIO so that the Discovery system does not have to sort 10,000+ items on the fly

 

Reporting

Data array extraction Metadb software version 1.4
See Metadb Project Issues Log

GDPR compliance for Metadb software version 1.5 See Metadb Project Issues Log

 

 

 

Public Library 

https://folio-org.atlassian.net/browse/UXPROD-5094

https://folio-org.atlassian.net/browse/UXPROD-5117

 

 

 

Data Export

https://folio-org.atlassian.net/browse/UXPROD-2708




Ability to edit a profile after it has been used (UXPROD-2708)

https://folio-org.atlassian.net/issues/UXPROD-2708?jql=ORDER%20BY%20created%20DESC

Ability to combine Instance data and SRS records (UXPROD-3254)

https://folio-org.atlassian.net/issues/UXPROD-3254?jql=ORDER%20BY%20created%20DESC

Ability to cancel a job (UXPROD-2328)

https://folio-org.atlassian.net/issues/UXPROD-2328?jql=ORDER%20BY%20created%20DESC

 

https://folio-org.atlassian.net/browse/ROAD-65

Linked Open Data

https://folio-org.atlassian.net/browse/UXPROD-4600

 

 

 

 

Implementers

https://folio-org.atlassian.net/browse/UXPROD-4776

https://folio-org.atlassian.net/browse/UXPROD-3822

 

 

 

Bulk Edit

UXPROD-4990  - Trillium - bulk edit performance improvements

UXPROD-4025 - Creating and Managing Bulk Edit Profiles for Scheduling Jobs

UXPROD-5277 - Token support in bulk edit profiles

UXPROD-4952 - Bulk edit - Scheduling bulk edit jobs

 

Data Import

Update Instance Administrative Data Only (https://folio-org.atlassian.net/browse/UIDATIMP-1724)

Allow update of the Instance and the SRS record in a single data import job (https://folio-org.atlassian.net/browse/MODDATAIMP-1199)

Allow for MARC field protection at the import profile level (https://folio-org.atlassian.net/browse/UXPROD-2934 )

Reporting: Have the ability to download a list of errors from an import (https://folio-org.atlassian.net/browse/UIDATIMP-914 )

Jobs run immediately after canceled jobs take excess time (https://folio-org.atlassian.net/browse/MODSOURMAN-970)

List App

 

 

 

 

 

Metadata Management

 

 

 

 

 

Resource Acccess

 

 

 

 

 

Ideas for Next Iteration

  • Two tier

    • Single rank list of vetted, shovel ready UXPRODs ranked by PC

    • Broad list of priorities submitted by community

    • Can PC include priorities that reflect technical debt? How would we get UXPRODs?

      • maybe these would be gaps against a baseline

  • Jira Dashboard

    • All priorities must have UXPRODs

      • Is it ok to create placeholder UXPRODs?

    • Only complete, dev ready UXPRODs can be included on PC list.

    • Flag UXPRODs in submitted by community that are high priorities for PC but need more work.

Ideas for Future Iterations

  • PC add priorities for gaps against established baseline

    • To accomplish this we need:

      • validated baseline

      • a process for getting these reflected in UXPROD - who is product owner? Do we ask SIGs to add them? etc

    • How to best reflect technical debt?

Proposed Distribution Plan

Long Term Goal - update and distribute this page quarterly in April, July, October, and January.

  • Beginning of the month - put out call to SIG liaisons

  • mid month - compile and review with PC

  • end of month - distribute to the community via Slack

  • add recurring agenda item for tri-council meetings and community updates

 

 

Review Notes

Observations

  • This was a big ask - we will need to give ample lead time and be patient as they ramp up this process

  • Not everyone submitted 5 - maybe top 3 would be more focused / lighter lift

  • Implementers and some subgroups wished to include their top 5

Review Questions

Content

  • How useful are these priorities? How can we make them more useful?

  • How does this track with our assumptions about FOLIO development priorities? Is there an additional PC perspective that needs to be reflected here?

  • Include scheduled work, unscheduled work, or break out both?

  • Are there other slices of priority information that would be interesting to have here?

Scope

  • Do we want to include priorities from subgroups as well as SIGs? What is the correct level of granularity?

  • How do we ensure “orphaned” groups are accounted for?

  • How do we capture different perspectives?

Format

  • Is it better to manage this in Jira or Confluence? If Jira, should we be tracking these priorities in PC Jira?

  • Would it be better to do top 3?

  • What is the best way to collate priorities - by SIG, by app, or something else?

Sources

Acquisitions

Metadata Management

Metadata Management Road Map → For a list of the top 5 anticipated features by votes, see the gadget Open and not Planned Metadata Management Features.

https://folio-org.atlassian.net/wiki/spaces/MM/pages/716243025

App Interaction | Cross App

https://folio-org.atlassian.net/wiki/spaces/AppInt/pages/712245249

https://folio-org.atlassian.net/jira/dashboards/10270 (Did not work for me - may need to be rebuilt or need permission tweak)

ERM

Bulk Edit

high level roadmap

Lists App

High level roadmap

Reporting

See Metadb Project Issues Log

Data Export

https://folio-org.atlassian.net/browse/ROAD-65

SIGs Not Yet Reflected Here

Related content