Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Compare and report dataset id and collection part in URI mismatch upon ingestion #5

Open
d0rg0ld opened this issue Nov 12, 2014 · 0 comments
Open

Compare and report dataset id and collection part in URI mismatch upon ingestion #5

d0rg0ld opened this issue Nov 12, 2014 · 0 comments
Labels
enhancement

Comments

@d0rg0ld
Copy link
Member

d0rg0ld commented Nov 12, 2014

Ingesting a dataset requires one to define a dataset id. This id has to match the "collection" part of the CHO URIS. If they mismatch, the dataset is rejected by Pubby, leading to ingested datasets that cannot be displayed, thus being lost in some kind of intermediate state. This is currently not reported to the user and therefore it would be good to check this at ingestion time.

@kaiec @kba
kba added a commit that referenced this issue Nov 15, 2014
@kba
Implemented dataset mismatch check before ingestion, factored XSLT tr…
f3a9dae 
…ansformation into method, #5
kba added a commit to DM2E/dm2e-ontologies that referenced this issue Nov 15, 2014
@kba
Validation categories for dataset mismatch, DM2E/dm2e-direct#5
6e8db5a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@d0rg0ld