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
Metadata from JWS archives is not read #22
Comments
Indeed, the library so far only reads meta data information precisely as given in the specification. For several reasons this fails for the file given in the archive. The main reason, since it does not have an xml declaration, the stream is invalid and rejected. But even if i were to allow for it, then we would still have the problem, that each entry has 2 metadata segments. And in that case you get only one of them:
instead of the other:
Additionally i so far only consider descriptions as valid, that contain:
By the way, since I only have limited support for rdf metadata, you should be able to do any advanced processing on it yourself. You should be able to get the full metadata document using: |
…at has a description or a creator as a valid description
I reported the issue to JWS. Is clearly a problem of their metadata.
Something is missing here. How can I get the full metadata? So for clarification: I could store additional things like for instance cvterms for entries inside of
But I would have to parse such things myself. Is this correct? |
correct. the omex description elements are very limited. But you could always just not use the description object that I provide and just upload your own rdf files and add them to the archive. Similarly you ought to be able to extract them as well. and parse them. |
I added an example of the JWS archives to the tests
#21
Currently, the metadata from this archives cannot be read with libCombine which gives
Despite metadata in the
metadata.rdf
(see below listed).This could be related to #18, i.e. that you only check for
metadata.xml
and not formetadata.rdf
other tools use to write the metadata.metadata.rdf:
The text was updated successfully, but these errors were encountered: