Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Goals
- Determine complexity of allowing for configuration of 001 generation (prefix + starting value)
- 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)
...
Overview | Approach | Module | Story Points | Jira ticket | ||||||
---|---|---|---|---|---|---|---|---|---|---|
Validation for authority local files |
| mod-inventory-storage | 2 sp | |||||||
Implement sequence number generation mechanism for authority local files (Sequences Approach) |
| mod-inventory-storage | 5 sp | |||||||
Implement sequence number generation mechanism for authority local files (Table with counter Approach) |
| mod-inventory-storage | 5 sp | |||||||
Authority file id validation |
| mod-quick-marc | 2 sp | |||||||
Local authority file selection |
| ui-inventory |
...
Settings application UI preview:
Endpoints:
POST: /authority-source-files/{id}/hrid
Description: Endpoint returns current hrid value and increment it.
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
{ "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)
|
| ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
One table for all authority files | All 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 |
...