Skip to end of banner
Go to start of banner

Data Import Roadmap: Ramsons, Sunflower, & beyond

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Long Term Goals

  • Data Import can consistently process large uploads in a single job, without failure, to support a library’s higher volume needs.

  • Large Data Import uploads can be processed at a dependable speed which does not unreasonably delay or hinder other data processing.

  • Data Import is intuitive for users to complete both common and unique processes with in-UI validation and detailed error messaging to promote proper usage.

  • Substantial documentation is available to support user understanding of Data Import’s capabilities.

👁️  Current State (September 2024)

In September 2024, a survey was shared with the Data Import Subgroup and the larger Metadata Management SIG as a pulse check to identify strengths and weaknesses in the current iteration of Data Import (all responders were running on Poppy release at the time of inquiry). The results of this survey are distilled into high-level bullets below:

Strengths:

  • Data Import module has been stabilizing over recent releases

  • Action profiles generally work as expected

  • Data Import is reliable for most common data-ingestion processes

Weaknesses:

  • Documentation is lacking

  • Large jobs can still be unreliable

  • Match profiles can do better to support partial matches and complex criteria

  • Hard to know exactly how a complex job profile will process

  • Lack of clear, actionable error messages

🔗 Project Themes

As we identify our Data Import goals and the work needed to reach them, we want to filter project ideas and concepts through the following themes:

Usability

  • Is the design and user experience of Data Import intuitive?

  • Are features of the app easily understood?

  • Is documentation clear, understandable, and accessible

Functionality

  • Does Data Import do what we expect it to do and does it do it well?

  • Does it "work"?

  • Do we need enhancements to support user needs?

Stability

  • Is Data Import stable in an average environment?

  • Does it crash in certain scenarios?

  • Is it consistent?

Performance

  • How quickly can Data Import jobs process?

  • Is memory/CPU usage well-managed?

  • Does it run well with average tenant setup?

🗓️  Roadmap Overview

Ramsons IN PROGRESS :

UXPROD-4348 - Getting issue details... STATUS

UXPROD-3556 - Getting issue details... STATUS

UXPROD-4081 - Getting issue details... STATUS

UXPROD-4469 - Getting issue details... STATUS

Sunflower UPCOMING :

UXPROD-4944 - Getting issue details... STATUS

UXPROD-4754 - Getting issue details... STATUS

UXPROD-4080 - Getting issue details... STATUS

UXPROD-4704 - Getting issue details... STATUS
*NOTE: Plans for Sunflower are not yet solidified as of 10/8/2024

Potential projects for Trillium, Umbrellaleaf, etc… FUTURE RELEASES :

Usability

UXPROD-4936 - Getting issue details... STATUS

UXPROD-4935 - Getting issue details... STATUS

UXPROD-4943 - Getting issue details... STATUS

UXPROD-4938 - Getting issue details... STATUS

UXPROD-4440 - Getting issue details... STATUS

+ various initiatives to create, enhance, and maintain Data Import documentation

Functionality

UXPROD-4937 - Getting issue details... STATUS

UXPROD-4933 - Getting issue details... STATUS

Stability

UXPROD-4929 - Getting issue details... STATUS

UXPROD-4927 - Getting issue details... STATUS

Performance

UXPROD-4926 - Getting issue details... STATUS

UXPROD-4928 - Getting issue details... STATUS

  • No labels