SKOS roundtripping - drops Broad Term and Related Term
|Assignee:||José Raddaoui Marín||% Done:|
|Category:||XML import / export|
|Target version:||Release 1.4.0|
|Google Code Legacy ID:||Tested version:|
The terms are there in the export SKOS XML, but are dropped on Import into AtoM.
#4 Updated by Jesús García Crespo over 9 years ago
See also user discussion:
#5 Updated by José Raddaoui Marín over 9 years ago
SKOS is exporting the term and its childrens as <skos:Concept>. But its parent and its relations are exported as <skos:broader> and <skos:related> inside the <skos:Concept> group.
In the import SKOS only adds the terms with <skos:Concept>, so parent and relations are being dropped.
Should I try to add this missing terms only with the url value, or should I add a <skos:Concept> group in the export for relations and parent too?
#6 Updated by Jessica Bushey about 9 years ago
Radda - David is going to respond. In the meantime, you might find this page interesting: [[http://www.ibm.com/developerworks/xml/library/x-think42/]]
#7 Updated by David Juhasz about 9 years ago
I'm going to break this into three pieces:
- Drop the <broader> tag from the "current" term when exporting
- Add "stub" SKOS concept for related terms in export
- Match terms based on "preferred" label on import, and create term if no match
I'll include more detail in the sub-task descriptions.
#11 Updated by Jessica Bushey about 9 years ago
- File Places-Tax.png added
- File Places-Tax-2.png added
- File alberta;sfSkosPlugin.xml added
- File alberta2;sfSkosPlugin.xml added
Still dropping use for, related and broad term on import.
I have attached screenshots:
places-tax.png is for term before export
places-tax-2.png is for term after import
alberta;sfSkosPlugin.xml is for term at export
alberta2;sfSkosPlugin.xml is for the term after import