Versions Compared

Key

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

...

Phased approach (covers Phase 1- 3) 

ReleaseDeliverablesJira Requirements
Quesnelia
  • Phase 1 - Define technical approach when creating/editing/deriving MARC bib/auth via quickMARC
  • Implement required MARC bib rules – structural based on LOC documentation
  • Implement required MARC authority rules – structural based on LOC documentation
  • Access to help documentation - UI only 

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUIQM-600

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODQM-388

Ramsons
  • Phase 1 - Implement MARC record validation when creating/editing/deriving MARC bib/auth via quickMARC
    • Includes ECS support 
    • LCCN structure validation
    • Global MARC bib / MARC authority rules validation via config file/API endpoint
    • Customize MARC bib/MARC authority rules validation per tenant via config file/API endpoint 
  • Continue to implement required MARC bib rules – structural based on LOC documentation
  • Continue to implement required MARC authority rules – structural based on LOC documentation
  • Authority control - Subject validation (stretch) 

Sunflower
  • Phase 1 - Complete implementation 
    • Logging 
    • Reporting
  • MARC punctuation handling 
  • Possibly expose authority control mapping rules 
  • Remove subfield 9 logic on linkable fields 

Trillium

Phase 2 - ISBN/ISSN validation  (can the existing tool be used?)

Phase 2 - Reporting (Lists app?) 


Umbrellaleaf

Phase 3a  - Data import support (including single record import)


Vetch

Phase 3b  - Data import support (including single record import) 


Feature Matrix - Phase 1

MODQM-388

FeatureDescription / Jira issue(s)Notes 

Global MARC bib rules validation that includes 

  • MARC tags (repeatable/non-repeatable) 
  • MARC tags (required/not required) 
  • MARC indicators (required/not required)
  • MARC subfields (repeatable/non-repeatable) 
  • MARC subfields (required/not required)
  • MARC subfield values?  
  • MARC fixed fields 
  • Help documentation link

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUIQM-600

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
key



  • Potential UI work to show help documentation

Global MARC authority rules validation that includes 

  • MARC tags (repeatable/non-repeatable) 
  • MARC tags (required/not required) 
  • MARC indicators (required/not required)
  • MARC subfields (repeatable/non-repeatable) 
  • MARC subfields (required/not required)
  • MARC subfield values? 
  • MARC fixed fields 
  • Help documentation link

  • No front-end dev
  • Potential UI work to show help documentation

Implement required MARC bib rules – structural based on LOC documentation


Select fields only. Will include FE/BE development.


Implement required MARC authority rules – structural based on LOC documentation


Select fields only. Will include FE/BE development.

Allow a tenant to clone/customize/override MARC bib global rules validation to create/edit/derive via quickMARC  


  • Potential UI work to show help documentation

Allow a tenant to clone/customize/override MARC authority global rules validation to create/edit via quickMARC


  • Potential UI work to show help documentation

Allow a user to view and edit a MARC bib/MARC authority that bypasses rules validation and has errors. Examples: a record imported via data import or direct to the db. 
  • No front-end dev

Track/log/display

  • Errors that prevent record from being saved 
  • Errors that do not prevent record from being saved 

  • Possible front-end work

Authority control validation support 



...