Bug #652
SKOS roundtripping - drops Broad Term and Related Term
Status: | Feedback | Start date: | 03/19/2013 | |
---|---|---|---|---|
Priority: | Medium | Due date: | ||
Assignee: | José Raddaoui Marín | % Done: | 100% | |
Category: | XML import / export | |||
Target version: | Release 1.4.0 | |||
Google Code Legacy ID: | Tested version: | |||
Sponsored: | No | Requires documentation: |
Description
The terms are there in the export SKOS XML, but are dropped on Import into AtoM.
Subtasks
History
#1 Updated by Jessica Bushey over 8 years ago
- File beachfront;sfSkosPlugin.xml
added
- File Beachfront-beforeexport.png added
- File Beachfront-afterimport.png added
I have attached xml file and before & after screengrabs.
#2 Updated by David Juhasz over 8 years ago
- Priority changed from Medium to High
- Target version changed from Release 2.1.0 to Release 1.4.0
#3 Updated by Jesús García Crespo about 8 years ago
- Assignee changed from David Juhasz to José Raddaoui Marín
- Sponsored set to No
#4 Updated by Jesús García Crespo about 8 years ago
See also user discussion:
https://groups.google.com/forum/?fromgroups#!topic/ica-atom-users/ogAyfJOhKJU
#5 Updated by José Raddaoui Marín about 8 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 8 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 8 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.
#8 Updated by José Raddaoui Marín almost 8 years ago
I've sent a fix to Jesús for #4814.
Now, what should I do with the related terms?
#9 Updated by Jesús García Crespo almost 8 years ago
- Status changed from New to QA/Review
#10 Updated by Jessica Bushey almost 8 years ago
- Assignee changed from José Raddaoui Marín to David Juhasz
#11 Updated by Jessica Bushey almost 8 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
#12 Updated by Jessica Bushey almost 8 years ago
- Status changed from QA/Review to Feedback
- Assignee changed from David Juhasz to José Raddaoui Marín
#13 Updated by David Juhasz almost 8 years ago
Jessica, in your sample data the "Use For" label "Western Canada" appears in "places-tax-2.png" and "alberta2;sfSkosPlugin.xml", so the use for functionality seems to be working.