-
Notifications
You must be signed in to change notification settings - Fork 7
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
Make lobid-alma data valid against JSON schema #1340
Comments
I spottet two errors in the validation process with the test data after running the updated script (#1344 ):
The first error is with every record the second is only with the one so far. |
@dr0i |
That's a "feature" as the test files, at whatever date created, comparable. It might be worth to think about using a valid dummy pattern, e.g. 0000-00-00T00:00:00 . Or you could expand the validator to allow "dummy". |
+1 for that |
Should be fine now. Closing. |
Again I run this with the updates from #1344:
Still errors |
The item error is due to #1177 |
List of things that do not validate:
these are the errors that appear while transforming via morph. |
This resulted in invalid json files with regard to the schema
At the moment there are three schema problems left:
|
Pathes that have invalid data after fixing describedBy (#2025 ) now:
Spatial source needs also to allow rpb spatial. publishedBy seems to be due to an faulty mapping: #2011 (comment) |
Concerning the missing subject labels for notations, we should ask ourselves if we drop label as mandatory for skosConcepts or introduce a third type of subject: notations which only need the notation, or we use the notation as fallback label if no label is provided. |
This is to allow institutions that are not specified by an ISIL as ebsco or proquest but have OCLC or ALMA institution codes. See #1438
I had a look at it again added a PR #2040 for spatial. #2027 (hasItem) I also saw that ajv is waring about the type schema: Additionally the decision for: (#1340 (comment))
is still open. After that the schema would be validate |
Schema: Adjust hasItem: loose constant value for type property #1340
Talked to @acka47 off board. We decided to introduce a mechanism that either requires a label and Id with option for notation, or an notation with option for label and Id so that the connection label and Id is always enforced. (Typing this I am not sure about DDC if this is succifient.) |
Finally done, closing. Next step: #1339 |
https://gist.githubusercontent.com/TobiasNx/007a32d61457dc57e353c5f1cd97a5e0/raw/4e9f525f114c0ab06279d28b2c70854cc5c6cee8/validationError.txt
This is an list of the errors of the test data.
The text was updated successfully, but these errors were encountered: