Current situation or problem:

For the Thin Thread release, anyone can access and use the module. In production, FOLIO will need to support user accounts and permissions for a number of purposes, including for the individual cataloger to keep track of work completed and to set preferences in the UI. 

In scope

• Follow / inherit how user permissions are created and supported in FOLIO

• Linked Data Editor-specific settings at the user level

  • e.g. Permissions around editing and governance of resource descriptions

Out of scope

Use case(s)

1. Cataloger

   • Ability to access the Linked Data Editor application through FOLIO

   • Ability to create new resource descriptions in the Linked Data Editor 

   • Ability to create / update Instance entity

   • Ability to create / update Work entity

2. Manager  

   1. Ability to run reports

   2. Ability to see output of cataloging for team

   3. Rules related to delete / staff suppress

   4. Ability to override changes made by a cataloger, including ability to change source type back to MARC (will likely be a new category)

3. System administrator

   • Ability to define a set of resource descriptions for export via the data export module in FOLIO

     • Temporal (day, week, month, custom)

     • Bibliographic parameter

     • Status (e.g. exclude resource descriptions that are suppressed from patron view)

   • Ability to save export queries

   • Ability to create, modify, delete validation rules that apply to resource descriptions

   • Ability to create, modify, delete import and export profiles

   • Ability to conduct bulk edit jobs

Proposed solution/stories

Links to additional info

Questions

Since the application will be available as a stand-alone module (interoperable with the FOLIO platform), what architecture decisions should be made to support user account for an institution without FOLIO?

Q: Is there information included in the bib record that shouldn't be displayed publicly? Could point to a requirement that prevents a user from unsuppressing the status

Q. Suppress - any cataloger can set suppress .