Data Import Community Minimal Viable Product (MVP)

From PC vision document

What functionality should FOLIO support?

Ability to import and export data across all areas of functionality, including connections with external systems (e.g., data import for inventory/acquisitions, APIs)
Queries and reports within and across different functional areas of FOLIO (e.g., lists, queries, connections to external reporting tools)

What is the user experience?

FOLIO users should experience a uniform and intuitive user interface and experience, which covers the following features:

Comfortable and diverse search functionality
Comfortable and flexible system configuration
Duplication and validation check, with meaningful error messages
Flexible customization of interfaces, templates, messages, layout of output to meet local library needs
Flexible workflow management
Roles, rights and permissions management;

What are some additional FOLIO features?

This final category is a compilation of non-functional/architectural considerations that make FOLIO a better product:

The architecture must be scalable and reliable, capable of working with large amounts of data
FOLIO should follow a modular concept, allowing for expansion or substitution of functionality to account for local or regional requirements
FOLIO should use APIs in support of interoperability. (e.g., for discovery, finance systems, student registry system, identity management, bibliographic databases, self-service systems, interlibrary loan, etc.)
FOLIO should meet all standard accessibility guidelines

Are there areas that are out-of-scope?

Although part of some LSPs, FOLIO does not offer functionality in the following areas, instead relying on APIs for third-party integrations: