-
Notifications
You must be signed in to change notification settings - Fork 0
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
edm:hasView is output in addition to edm:isShownAt #105
Comments
The problem here is that the uber/dingler data contain patterns like
with Now, the DM2E model defines
Hence, the DM2E-EDM converter notices that
Unless the DM2E model skips subclassing |
I think the best solution would be to skip any subclassing of |
I actually have a different proposal: hasAnnotatableVersion should be very close to "isShownBy". So I'd suggest to convert hasAnotatableVersionAt to isShownBy whenever there is no isShownBy Property assigned right away. |
otherwise skip of course |
In case of dingler the URIs for |
I think that the Dingler case is rather special in this regard, as you link to the "isShownAt" html representation for annotation, which was also noted by Net7 in #47 |
I had a brief look at the data and a chat with Julia. In most cases, dm2e:hasAnnotatableVersionAt is assigned to page level CHOs and should therefore be no issue for Europeana ingestion. For the few cases where hasAnnotatableVersion is assigned to objects on item level, it cant be clearly distinguished whether they should be assigned to isShownAt or isShownBy. Therefore I now also propose to skip the subclassing of hasAnnotatableVersionAt ... |
…bleVersionAt no longer subclassed, DM2E/dm2e-mappings#105
…elete properties after All-WP Bergen), DM2E/dm2e-mappings#105
Might be a bug in the super-property logic in Dm2e2Edm
The text was updated successfully, but these errors were encountered: