DUO codes are not in standard format

vildead commented 2 years ago

The suffix [XX] in DUO some of the codes is a placeholder for more detailed machine actionable definition of the restriction. E.g. geographical restriction to Europe can be recorded as GS-[EU]

While this is nice feature, implementing this dynamic behaviour would require some work.

[x] clean the codes and remove the optional suffixes (they make a mess in other tools where a real value is expected instead of XX).
[ ] record ids of the ontology terms (e.g. DUO:0000022) - labels/codes are less stable and any matching would be simpler on the ID. Align with official DUO mapping

thanks Danielle for great input!

vildead commented 2 years ago

comment from Pinar: i was meaning to create an issue somewhat related to this. What we have in Daisy is Ga4gh consent codes described in some paper. DUO is the Follow up to consent codes and is encoded in owl ( web ontology language) 11:18 İn short we should migrate from consent codes to duo in DAlSY. 11:20 İn the “code” field of the db table we could keep the identifiers of DUO classes. Or whatever would be the best practice. Jacek may comment.

vildead commented 10 months ago

related to #462 MR removes the XX and CC placeholders

elixir-luxembourg / daisy

DUO codes are not in standard format #328