sid/tatus at main · Hsinbyushin/sid · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
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
[1mdiff --git a/README.md b/README.md[m
[1mindex a130654..a97cac7 100644[m
[1m--- a/README.md[m
[1m+++ b/README.md[m
[36m@@ -37,9 +37,9 @@[m [mSID is being designed around a number of core principles:[m
 - extensibility to additional libraries, catalogues, vendors, and workflows.[m
 [m
 [m
[31m-## Planned Workflow[m
[32m+[m[32m## Acquisition Workflow[m
 [m
[31m-The intended acquisition workflow is:[m
[32m+[m[32mSID's acquisition workflow is organized around the following stages:[m
 [m
 ```text[m
 Order Plan[m
[36m@@ -72,10 +72,19 @@[m [mBudget Management[m
 Order List Export[m
 ```[m
 [m
[31m-Vendor documents may eventually include formats such as XLSX, CSV, and PDF.[m
[32m+[m[32mSID currently includes a StaBiKat (Catalog of Staatsbibliothek zu Berlin)[m
[32m+[m[32madapter using the K10plus SRU/MODS interface.[m
 [m
[31m-The parsing architecture will be developed against representative real-world[m
[31m-vendor documents rather than assumptions about their structure.[m
[32m+[m[32mCatalogue responses are normalized into SID's internal catalogue record[m
[32m+[m[32mrepresentation before matching takes place. Vendor offers can be checked[m
[32m+[m[32magainst the configured catalogue from the acquisition-selection workflow.[m
[32m+[m
[32m+[m[32mCatalogue checks run independently from vendor-document interpretation:[m
[32m+[m[32mstructured identifiers extracted from vendor data are used directly for[m
[32m+[m[32mcatalogue lookup whenever possible.[m
[32m+[m
[32m+[m[32mThis separation allows other libraries to provide adapters for their own[m
[32m+[m[32mcatalogue infrastructure without changing SID's acquisition domain.[m
 [m
 [m
 ## Acquisition Planning[m
[36m@@ -164,13 +173,10 @@[m [mwhere required and must never silently replace the original text.[m
 [m
 ## Language Models[m
 [m
[31m-Language models may eventually assist with ambiguous or poorly structured vendor[m
[31m-documents.[m
[32m+[m[32mSID supports optional local language-model assistance for ambiguous or poorly[m
[32m+[m[32mstructured vendor data.[m
 [m
[31m-They are not intended to replace deterministic parsing where reliable structured[m
[31m-information is available.[m
[31m-[m
[31m-A future parsing architecture may therefore use:[m
[32m+[m[32mThe parsing architecture follows this general separation:[m
 [m
 ```text[m
 Structured / deterministic parsing[m
[36m@@ -211,20 +217,30 @@[m [madvantage.[m
 [m
 ## Project Status[m
 [m
[31m-SID is currently under active early development.[m
[32m+[m[32mSID is currently under active MVP development.[m
 [m
[31m-The first MVP focuses on establishing:[m
[32m+[m[32mThe application already provides foundations for:[m
 [m
[31m-- acquisition plans;[m
[31m-- order lists;[m
[31m-- budget management;[m
[31m-- the planning dashboard;[m
[32m+[m[32m- acquisition plans and order lists;[m
[32m+[m[32m- budget-aware acquisition planning;[m
[32m+[m[32m- deterministic DOCX extraction;[m
[32m+[m[32m- vendor-specific parsing of representative Mary Martin offer lists;[m
[32m+[m[32m- preservation and validation of extracted bibliographic and commercial data;[m
 - catalogue-provider abstractions;[m
[31m-- bibliographic domain foundations;[m
[31m-- security and validation foundations.[m
[31m-[m
[31m-Document parsing will be implemented after representative vendor files have been[m
[31m-examined.[m
[32m+[m[32m- StaBiKat lookup through the K10plus SRU/MODS interface;[m
[32m+[m[32m- catalogue matching based on extracted identifiers;[m
[32m+[m[32m- asynchronous, batched catalogue checks from the LiveView selection workflow;[m
[32m+[m[32m- catalogue-status filtering during selection;[m
[32m+[m[32m- Unicode and multiscript bibliographic data;[m
[32m+[m[32m- optional local semantic interpretation for ambiguous vendor data.[m
[32m+[m
[32m+[m[32mThe current end-to-end development workflow can import a vendor DOCX file,[m
[32m+[m[32mextract its offers, display them within an order list, check available[m
[32m+[m[32midentifiers against StaBiKat, and present the resulting catalogue status for[m
[32m+[m[32mreview.[m
[32m+[m
[32m+[m[32mSelection decisions, persistent imported offers, complete budget allocation,[m
[32m+[m[32morder export, and broader vendor/catalogue support remain under development.[m
 [m
 [m
 ## Architecture[m