What DUO is for
Repositories and data stewards can annotate data with use permissions or restrictions. Researchers can describe intended use. Systems can then support consistent discovery and preliminary matching across datasets and requests.
Terms and identifiers should be taken from the current ontology release and repository implementation. Local shorthand should not be allowed to silently change the meaning of a code.
Evaluate the proposed purpose
Capture the release's proposed DUO codes and compare them with the data-use terms confirmed for the governing agreement. Treat mismatches as explainable findings that identify expected and proposed values. Route the result to the authorized committee or steward.
Combine DUO with Library Cards
GA4GH Library Cards can represent institutional assertions relevant to access. Audarel can require active institutional pre-authorization for named users on the planned release date while separately evaluating DUO purpose terms.
Keep the human decision visible
Ontology matching can reduce administrative work, but context and exceptions still require governance judgment. Record the reviewer or committee, comments, quorum, time, agreement version, proposed codes, and final release decision.
Keep decisions human and evidence explicit.
Practical guidance that connects policy documents to observable release controls.
Confirm requirements against current source material.
Requirements and vendor capabilities change. Confirm the current source and your approved QC plan before changing a production process.