Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Suggested A similar result may be 



well, yes, there is not a clone so the quickest thing that comes to my mind is to go through a SPARQL update, possibly getting all concepts under a certain one (using the star operator with skos:broader), copying everything from the source concepts into the new ones except references to the new concepts themselves (at least those through, again, the skos:broader property), for which a new URI must be minted, possibly basing on the previous one, with a bind e.g.

bind(IRI(concat(str(?oldURI), “_new”)) as ?newURI)

 This is the general idea, then it can be as simple or complex as needed. The update can then be stored as a parameterized SPARQL update (the parameter is the root of the branch to be cloned), so that conveniently, when invoking the stored parameterized update, the new root can be chosen through the UI




Create a new classification based on a new schema, class, etc...

...

  1. Go to menu Data, tab Concept
  2. In the left panel, browse/search for the concept you want to delete. Select it
  3. Click in the right panel, click on the downward pointing arrow next to the cogwheel
    1. click on Set as deprecated

In The blu ball next to the Concept name (in both panels) will become grey and in box “Other properties” , will appear (right panel) you will see a property “owl:deprecated" with value "true”  



Restore a deprecated item 

Delete the property owl:deprecated, in box "Other properties", right panel 



Bulk operations with Shee2RDF

...