-
Notifications
You must be signed in to change notification settings - Fork 13
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
conflicting namespace prefixes during ListRecords #36
Comments
Thanks for the detailed bug report - that's certainly an interesting issue and I'll try to take a look at it shortly - it may also be some issue in the stdlib, as per golang/go #48641. |
I'm afraid this is a Go stdlib XML issue first, cf. golang/go#13400. But then, metha is mostly concerned with the envelope and that should be much less problematic. This will requires some internal rewrite and may take a while before it is released, just as a heads up. |
If you do a harvest during which the same prefix will be seen with different URL targets, metha-sync will jumble the prefix – suffixing it by
1
but never declaring that renamed prefix, so the resulting XMLs become invalid.For example, if I do
then (because in our MODS the namespace for the extension
slub
has been changed some time ago and now appears in some records with declarationhttp://www.slub-dresden.de/namespace
but withhttp://www.slub-dresden.de/
in others) I end up with altered and non-wellformed METS files. For example inoai:de:slub-dresden:db:id-1840307358
, instead of……(which is what you get for a single GetRecord request) I now see…
…(which is invalid, because
slub1
has never been introduced).The text was updated successfully, but these errors were encountered: