SRS Requirements

	A	B	C	D
1	SRS Requirements
2
3	Requirement	Related app(s)	Who added?	Notes (add your initials at the beginning of the note!

4	Accessible by Inventory to serve as Inventory record base when Source = MARC	Inventory	A-M	A-M: Instance for now; Inventory holdings in future
5	Allows for the display of a human-friendly MARC record when an Inventory user selects View source, and Source = MARC	Inventory	A-M	A-M: Instance for now; Inventory holdings in future
6	Allows Inventory Instance to update the Suppress from discovery flag in metadata of SRS MARC	Inventory	A-M	A-M: Bib only for now; Holdings in the future
7	Supplies SRS MARC in response to OAI-PMH request	OAI-PMH	A-M	A-M: Bib only for now, Holdings in the future
8	Supplies SRS MARC in response to FOLIO Data Export request	Data Export	A-M	A-M: Bib only for now; Holdings in the future
9	Store MARC records added to MARC via Data Import or MARCcat	Data Import, MARCcat	A-M	A-M: Bib only for now; Holdings and Authority in the future
10	Allow quickMARC to access MARC Bib records, update them, and save updates	quickMARC	A-M
11	Allow MARCcat creates and updates to be reflected in SRS MARC Bibs	MARCcat	A-M	A-M: Starting with Bibs; Holdings and Authority in the future
12	Pass SRS MARC creates and updates to MARCcat, so that they stay synchronized	MARCcat	A-M	A-M: Starting with Bibs; Holdings and Authority in the future
13	Receive and store other types of source data in the future	Data import	A-M	A-M: MARC for now, EDIFACT, Delimited coming; then perhaps EAD, BIBFRAME
14	Make SRS data accessible to the LDP and other reporting services	LDP, Reporting	??
15	Would SRS come into play for Orders and Invoices, or would that be SRM and MODDI?	Orders, Invoices	??	A-M: Incoming data in MARC, delimited, EDIFACT files would be used to create orders and create/update invoices. That incoming data would be stored, but unlike the SRS-Inventory relationship, orders and invoices don't have to be kept in sync with any SRS data.
16	Data Import/SRM should support the creation of links between MARC bib records and MARC holdings records	Data Import	TAMU	UXPROD-1575 and related jira tickets leave open the question of whether MARC bibs and MARC holdings will be directly linked. Such links should be created when MARC holdings are loaded initially and maintained throughout the life of the MARC records A-M to find info on the 014 handling in the MARC holdings record
17	SRS should maintain direct links between MARC bib records and MARC holdings records	SRS, MARCCat	TAMU	UXPROD-1575 and related jira tickets leave open the question of whether MARC bibs and MARC holdings will be directly linked. Such links should be created when MARC holdings are loaded initially and maintained throughout the life of the MARC records. A-M: How much link do we need in SRS versus letting Inventory manage the links and relationships between Instances (Bibs) and Holdings?
18	No interactions with Agreements, Licenses, eHoldings, Reserves		A-M	A-M: Maybe in the future? Nothing concrete at this point
19	Data import API should support a "first time" or migration load	Data Import	TAMU	For migration, the data import API doesn't need to create versioned records. A-M: what does "support" mean in terms of requirements? This is beyond Data Import's original scope, and specifically excluded in how the HRID handling is currently specified
20	Data import performance should remain consistent across a large number of batches	Data Import	TAMU
21	Data import should support a batch size of up to 10,000 records	Data Import	TAMU
22	Data import performance should be at least 300 records/sec	Data Import	TAMU	For migration, this would allow for the loading of 1,080,000 records/hour. This is the minimum performance required.
23	Data import should allow setting the inventory UUIDs from the source record	Data Import	TAMU	This would support consistent data sets for migration
24	Data import should return the inventory UUIDs in the log	Data Import	TAMU	This would support consistent data sets for migration
25	Data import error reporting should return the 001, position in source file, and some explanation for all errors in a batch	Data Import	TAMU
26	Ability to query SRS by ??? (what all types of queries?)	Data Export, OAI-PMH, Inventory?, Other?	Oleksii	Taras: queries only efficient by date, Instance/SRS UUID; others will not be; might need ElasticSearch or something else for more complex; full-record queries, rather than indexes; don't use pagination; stream data using http2 fxn perhaps A-M: would matching be a kind of queries? e.g. matching on the 035 field, or 020 $a, or 001, etc?
27	Data import "Batch functionality" must be used by library staff on a regular basis		Taras
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100