-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Avram format to express schema #1
Comments
nichtich
added a commit
to pkiraly/qa-catalogue
that referenced
this issue
Nov 24, 2023
As listed at <timathom/marc-schema#1>: - wrap the list of fields in a root object with key 'fields' and add key family with value 'marc' - rename key 'name' to 'label' - rename key 'values' to 'codes' - remove key 'fixed', its value is implied by non-existence of 'subfields'
nichtich
added a commit
to pkiraly/qa-catalogue
that referenced
this issue
Nov 24, 2023
As listed at <timathom/marc-schema#1>: - wrap the list of fields in a root object with key 'fields' and add key family with value 'marc' - rename key 'name' to 'label' - rename key 'values' to 'codes' - rename key 'staticValues' to 'positions' - remove key 'fixed', its value is implied by non-existence of 'subfields'
This was referenced Nov 24, 2023
nichtich
added a commit
to pkiraly/qa-catalogue
that referenced
this issue
Nov 24, 2023
As listed at <timathom/marc-schema#1>: - wrap the list of fields in a root object with key 'fields' and add key family with value 'marc' - rename key 'name' to 'label' - rename key 'values' to 'codes' - rename key 'staticValues' to 'positions' - remove key 'fixed', its value is implied by non-existence of 'subfields'
In addition rename key |
nichtich
added a commit
to nichtich/marc-schema
that referenced
this issue
Nov 26, 2023
- name to label - value to code - staticValues to codes - values to positions
Merged
pkiraly
added a commit
to pkiraly/qa-catalogue
that referenced
this issue
Dec 7, 2023
* First steps to convert MARC schema to Avram format As listed at <timathom/marc-schema#1>: - wrap the list of fields in a root object with key 'fields' and add key family with value 'marc' - rename key 'name' to 'label' - rename key 'values' to 'codes' - rename key 'staticValues' to 'positions' - remove key 'fixed', its value is implied by non-existence of 'subfields' * First steps to convert MARC schema to Avram format #371 --------- Co-authored-by: Péter Király <[email protected]>
This was referenced Dec 12, 2023
This can be closed with #12 although some errors remain - I will open independent issues for these. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The schema format can be changed without much modification to comply with Avram format. Seems like independent invention of a MARC schema format resulted in very similar outcome, so it must be good.
fields
and add keyfamily
with valuemarc
covered by Extend migration to Avram format #7
leader
toLDR
covered by Extend migration to Avram format #7
fixed
, its value is implied by existence ofsubfields
covered by Extend migration to Avram format #7
name
tolabel
values
tocodes
andvalue
tocode
indicators
with keys1
and2
toindicator1
andindicator2
positions
to an Avram position objectstaticValues
tocodes
.static
, it is implied by existencestaticValues
covered by Extend migration to Avram format #7
By the way feedback to the specification is appreciated. Final version 1.0 should be released in 2024 with formal test suite.
The text was updated successfully, but these errors were encountered: