Versions Compared

Old Version 40

changes.mady.by.user Kalibek Turgumbayev

Saved on

compared with

New Version 41

changes.mady.by.user Christine Schultz-Richert

Saved on

Key

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

Jira Legacy
serverSystem JiraFOLIO Issue Tracker
serverId01505d016ccf3fe4-b8533301-3c2e368a-90f1983e-ee9b165564fc20c466b11a49
keyMODQM-311

Goals

  1. Determine complexity of allowing for configuration of 001 generation (prefix + starting value) 
  2. Adding the ability to select the desired authority source file at point of creation of new record (so the system would know how to generate the 001 per the configuration)

...

OverviewApproachModuleStory PointsJira ticket
Validation for authority local files
  1. New parameter 'startNumber' for authority source file creation is presented 
  2. Implement AuthoritySourceFileHridManager with Validation:
      - (if source = 'local' then codes.size = 1) else throw exception
      - (if source = 'local' and startNumber = null) set startValue = 1
      - prevent user to update "start with" after file creation
mod-inventory-storage3 sp


Jira Legacy
serverSystem JiraFOLIO Issue Tracker
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d016ccf3fe4-b8533301-3c2e368a-90f1983e-ee9b165564fc20c466b11a49
keyMODINVSTOR-1049
Status
colourGreen
titleApproved

Implement sequence number generation mechanism for authority local files (Sequences Approach)





  1. New endpoint to catch-up authority current hrid information is presented
  2. Extend AuthoritySourceFileHridManager to work with sequences
      - Create sequence for authority local file after validation
      - Update sequence name for authority local file if prefix was updated
      - Drop sequence for authority local file after deletion
  3. Return hrid on request 
      - Retrieve next value from localFile sequence 
      - Format next value to NaturalId(HRID) format
mod-inventory-storage5 sp

Jira Legacy
serverSystem JiraFOLIO Issue Tracker
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d016ccf3fe4-b8533301-3c2e368a-90f1983e-ee9b165564fc20c466b11a49
keyMODINVSTOR-1050

Status
colourRed
titleDeclined

Implement sequence number generation mechanism for authority local files (Table with counter Approach)


  1. New endpoint to catch-up authority current hrid information is presented
  2. New table to work with authority files HRID presented
  3. Extend AuthoritySourceFileHridManager to work with table
      - All transactions should be done with SERIALIZABLE isolation
      - On request return current hrid value and increment it. 
      - Format value to NaturalId(HRID) format
mod-inventory-storage5 sp
Authority file id validation
  1. mod-quick-marc in scope of authority creation should convert 001 field value to UUID and retrieve available hrid for source file id.
  2. Replace 001 field value from authorityFileId to "prefix + hrid"
  3. If 001 value doesn't comply with UUID then skip it. And leave the original value
mod-quick-marc2 sp

Jira Legacy
serverSystem JiraFOLIO Issue Tracker
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d016ccf3fe4-b8533301-3c2e368a-90f1983e-ee9b165564fc20c466b11a49
keyMODQM-322

Local authority file selection
  1. User should have the ability to look-up for local authority file
    (As permanent-location look-up for Holdings)

  2. UI should put authorityFileId to 001 field
ui-inventory

Jira Legacy
serverSystem JiraFOLIO Issue Tracker
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d016ccf3fe4-b8533301-3c2e368a-90f1983e-ee9b165564fc20c466b11a49
keyUXPROD-3910

Ability to store authority local files

Settings application UI preview:

localauthoritydefinition.PNG

Endpoints:

POST: /authority-source-files/{id}/hrid
Description:  Endpoint returns current hrid value and increment it. 

Code Block
themeDJango
borderStyledashed
titleAuthority Source File HRID Example
collapsetrue
{
    "id": "cb58492d-018e-442d-9ce3-35aabfc524aa",
    "prefix": "loc",
    "hrid": "000000001"
}

POST: /authority-source-files
New query parameter: startNumber (default = 1)

...


To work with table it's better to use SERIALIZABLE Isolation:
@Transactional(isolation = Isolation.SERIALIZABLE)

Status
colourGreen
titlePros

Status
colourRed
titleCons

One table for all authority filesAll work with select and increment should be done manually.

Harder work with transactions. 
All transactions should be fulfilled in SERIALIZABLE Isolation level. So it can reduce performance

...

  • We also need to warn the user that field 001 may be overwritten by field 010.


Q/A section

QuestionStatusAnswerNotes
How many files can be per one tenant? Do we expect millions of files? Can we restrict amount of authority files per tenant?

Status
colourYellow
titleopen

We can likely expect less than 10 local authority files to be created. Typically, records are created for local files for use cases such as:

  • A record does not yet exist in an external/national database (for example, a university library may have items in their collections written by alumni for which the Library of Congress does not have a name authority record)
  • A record exists in an external/national database but the headings do not align with the mission/objectives of the institution (such as headings for indigenous peoples)



Do we expect authority records matching with local authority file during DI process?

Status
colourYellow
titleopen

Yes, it is possible for the library to want to update an existing local authority record via DI and would need to match on the existing file.