Bug #652

SKOS roundtripping - drops Broad Term and Related Term

Added by Jessica Bushey almost 9 years ago. Updated over 8 years ago.

Status:FeedbackStart date:03/19/2013
Priority:MediumDue 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.

beachfront;sfSkosPlugin.xml Magnifier (3.12 KB) Jessica Bushey, 11/27/2012 03:51 PM

Beachfront-beforeexport.png (23 KB) Jessica Bushey, 11/27/2012 03:51 PM

Beachfront-afterimport.png (22.1 KB) Jessica Bushey, 11/27/2012 03:51 PM

Places-Tax.png (51.9 KB) Jessica Bushey, 03/26/2013 10:44 AM

Places-Tax-2.png (46.5 KB) Jessica Bushey, 03/26/2013 10:45 AM

alberta;sfSkosPlugin.xml Magnifier (2.52 KB) Jessica Bushey, 03/26/2013 10:45 AM

alberta2;sfSkosPlugin.xml Magnifier (2.39 KB) Jessica Bushey, 03/26/2013 10:46 AM

Subtasks

Bug #4814: SKOS ignore <broader> tag for the top-level term in a hie...VerifiedJosé Raddaoui Marín

Feature #4867: SKOS XML should include "stub" Concept for related termsWon't fixJosé Raddaoui Marín

History

#1 Updated by Jessica Bushey almost 9 years ago

I have attached xml file and before & after screengrabs.

#2 Updated by David Juhasz almost 9 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 over 8 years ago

  • Assignee changed from David Juhasz to José Raddaoui Marín
  • Sponsored set to No

#5 Updated by José Raddaoui Marín over 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 over 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 over 8 years ago

I'm going to break this into three pieces:

  1. Drop the <broader> tag from the "current" term when exporting
  2. Add "stub" SKOS concept for related terms in export
  3. 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 over 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 over 8 years ago

  • Status changed from New to QA/Review

#10 Updated by Jessica Bushey over 8 years ago

  • Assignee changed from José Raddaoui Marín to David Juhasz

#11 Updated by Jessica Bushey over 8 years ago

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 over 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 over 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.

Also available in: Atom PDF