Details
-
Story
-
Status: Open (View Workflow)
-
P3
-
Resolution: Unresolved
-
None
-
-
5
-
Spitfire
-
Quesnelia (R1 2024)
-
TBD
Description
Purpose
This story focuses on updating the POST endpoint of the Authority-Source-Files API to accommodate a revised schema for the request body. The new schema includes specific constraints such as creating records with a "local" source and a single prefix. Additionally, the ability to specify the start number for the HRID sequence is included.
Approach
- Develop a new schema for the POST request body of the Authority-Source-Files API.
- Allow the creation of records only with a "local" source and a single prefix only.
- Implement functionality to specify the start number for the HRID sequence and creating a sequence.
- Add sequence_name varchar field to authority_source_file table.
- Add selectable boolean field to authority_source_file table with default false.
Request Body Example:
{ "id": "uuid", "name": "string", "code": "string", "type": "string", "baseUrl": "string", "selectable": true, "hridManagement": { "startNumber": 1 } }
Required fields: name, code
Default values: selectable=true, startNumber=1
Remove existing "required" constraints for non-required fields
"source" in database should be required
Acceptance criteria
- Covered by unit tests
- Module documentation updated
- Logging is well-defined
TestRail: Results
Attachments
Issue Links
- defines
-
MODQM-311 SPIKE: Investigate feasibility of local authority source support
-
- Closed
-
-
UXPROD-3910 Create a MARC authority record via quickMARC UI
-
- In progress
-
- has to be done before
-
MODELINKS-122 Implement Next Available HRID Endpoint for Authority File
-
- Open
-
-
UIMARCAUTH-337 Create new settings options for configuring authority files
-
- Open
-
-
UIMARCAUTH-360 CREATE | Create new settings options for configuring authority files
-
- Open
-
- mentioned in
-
Page Loading...