In-depth practical guides

Check the licence before reusing data

Connect each resource to its exact licence and retain attribution, version and relevant obligations.

Updated :

Legal research space with reference books and files.

AI-generated illustration

Does the licence cover the exact resource being reused?

Public access does not mean unconditional reuse. A platform may host different licences; text, data, software, images and third-party material may follow different terms.

  1. Identify the resource

    Open the used file or record page. Note named rights holder, licence, version and full text URL. Do not substitute portal terms for the file licence.

  2. Read obligations

    Licence Ouverte and CC BY require attribution under their terms. ODbL also sets conditions for adapted databases and certain public uses. Read the text for your reuse.

  3. Prepare publication

    Prepare visible attribution, licence link and change notice when required. Check personal data, third-party rights and trademarks separately. A data licence does not settle all these issues.

Reading workshop

Credit the chart and handle the photo separately

File DEMO-L04 prepares separate decisions for objects with different provenance on the same page.

Fictional data and records for learning: none of these results comes from a live service query.

A chart derived from CSV and an expressly excluded image

CSV v1 carries a CC BY 4.0 notice. The chart filters columns and aggregates values; the adjacent photo has an explicit exclusion requiring an independent decision.

  1. CSV DEMO-L04

    Scenario data
    File v1 explicitly under CC BY 4.0
    Diagnosis
    The stated scope is this file.
    Decision
    Retain source page and licence.
  2. Derived chart

    Scenario data
    Column filtering and aggregation
    Diagnosis
    Transformation does not remove provenance.
    Decision
    Prepare credit, source, licence link and changes.
  3. Third-party photo

    Scenario data
    Notice: image excluded from CSV licence
    Diagnosis
    Proximity does not transfer permission.
    Decision
    Do not reuse the photo; clarify its terms.
  4. Credit to review

    Scenario data
    DEMO author; Table L04; v1
    Diagnosis
    Credit must not imply producer endorsement.
    Decision
    Check supplied information and other rights.

Which deliverable respects this case’s scope?

Open each proposition to compare its diagnosis. More checks may still be needed.

One CC BY licence for the whole page.

No: the image is explicitly excluded.

A chart without provenance because values are grouped.

No: transformation does not make origin irrelevant.

Chart credit and a separate photo decision.

Appropriate. Retain unresolved questions; this record is not blanket permission.

Filled fictional record

File: DEMO-L04
Resource: Table L04; DEMO author; v1
Fictional source: https://example.invalid/donnees/L04
Licence: CC BY 4.0
Changes: filtered columns and aggregation
Planned credit: author, title, source, licence, changes
Third-party photo: excluded; not reused

Link the credit to the file version used and the retained licence text. Record chart transformations and keep the photo exclusion in the object register.

Documentation of the rules, separate from fictional examples

Compare other situations and exercises

Missing licence

Do not infer permission from a download button; find the producer’s licence or request clarification.

Map from a database

Distinguish map attribution from adapted database conditions; check ODbL terms and producer policy.

READING / ANNOTATED CASE

A credit that is too short for a composite resource

In this fictional case, “Atlas Demo” publishes table D-42 under CC BY 4.0 and explicitly excludes a third-party photograph. You plan a chart from two columns; its credit only says “Source: internet”. The table below prepares the review and grants no permission.

Fictional example · no observation of a service or client.

On small screens, scroll the table horizontally.

A credit that is too short for a composite resource
CheckSource noticePlanned publicationCorrection to prepare
ProvenanceAtlas Demo · table D-42 · version v2.“Source: internet”.Name the organisation and link the exact table.
LicenceCC BY 4.0 for the table.No licence link.State the licence and link to it.
ChangesTwo columns extracted from the table.Chart with shortened labels.Describe extraction and label changes; retain supplied notices.
ScopeThird-party photograph explicitly excluded.Reuse of that photograph is planned.Check its rights separately before use.
Does the chart credit also authorise the photograph?

No. In this example the photograph is excluded from the table licence. Its status needs a separate check.

Can provenance be removed after transforming the data?

Transformation does not remove the need to read applicable terms. For CC BY 4.0, check attribution and indication of changes in section 3 of the official legal code.

References accessed on

Worked exercise

A CSV licence does not automatically cover its photo

Fictional example: the values and documents teach the method and do not describe a real organisation.

You want to publish a chart based on the CSV and reuse the photograph on the same page. Terms apply to the objects shown.

If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.

Starting information
ObjectDisplayed terms
CSVCC BY 4.0
PhotographSeparate terms

Your checks

  1. Match each object to its exact licence.
  2. Prepare chart attribution and disclose transformations.
  3. Check photo terms separately.
Read the answer

Answer and decision

Treat two objects, not a blanket page permission. For CC BY material, prepare credit, reference and licence link with applicable change indications. Proximity does not give the photo that licence; assess its own reuse terms.

If the case changes

Third-party rights or personal data can require permissions the licence does not automatically supply.

Record to retain

Keep file, licence scope, text version, attribution and unresolved question.

Documentation reference : Creative Commons — CC BY 4.0 legal code · Consulted on

DOCUMENTED REFERENCE

SPDX: read a license choice without inventing permission

An SPDX expression combines identifiers and operators. Link the declaration to an exact version and scope: repository, package or file. These expressions illustrate syntax; they do not state this website’s license.

MITApache-2.0BSD-3-ClauseANDOR
SPDX: read a license choice without inventing permission
ReferenceValue or formWhat it identifies
MIT OR Apache-2.0ORA choice between declared licenses. Obligations of the selected license still apply.
MIT AND BSD-3-ClauseANDBoth licenses apply together to the stated scope; AND does not mean choosing the more permissive one.
GPL-2.0-only WITH Classpath-exception-2.0WITHA license with a named exception, not a general operator joining two independent licenses.
LicenseRef-23LicenseRef-A reference to license text defined in the SPDX document. Retrieve the definition; the name alone is insufficient.
MIT AND (Apache-2.0 OR BSD-3-Clause)( )Parentheses require choosing within the group before combining with MIT.
WITH > AND > ORprecedenceWITH binds before AND, which binds before OR. Preserve uppercase operators and parentheses.

Implication for the record

Check license text, exceptions and covered files. A recognised identifier or valid expression does not establish the declarant’s rights, component compatibility, or identical licensing for software, content, data and trademarks.

Primary documentation

Documentation consulted on .

Record to retain

  • Exact resource, rights holder and downloaded version.
  • Licence text, version, URL and access date.
  • Planned attribution, transformations and additional checks.

Official references

Related source profiles

Related protocols

Checks before reaching a conclusion

  • Are licence and version linked to the exact resource?
  • Does the planned attribution include required information and changes?
  • Have excluded and third-party elements been reviewed separately?

Frequently asked questions

Can licences be combined?

Assess compatibility and each obligation. Keep resource-level provenance rather than assigning one licence without justification.

Does an API change the licence?

Access method and rights differ: check API terms and the data licence.

Is the opening of the download equal to a reuse permit?

Access and reuse conditions are two distinct information. Find the references associated with the resource allows you to review the published framework without deducting it from its sole availability.

TOOLS / REGISTERS

Information to record

Prepare visible attribution, licence link and change notice when required. Check personal data, third-party rights and trademarks separately. A data licence does not settle all these issues.

  • Access date and time zone
  • Exact URL
  • Document identifier
  • Producer / publisher
  • Version / revision
  • Licence / reuse rights
  • Planned attribution and licence link
  • Method / definition
  • Limit / uncertainty
  • Decision / next action
  • Review owner
  • Next review

DOCUMENTED REFERENCE

Digitised heritage: a rights statement is not a licence

RightsStatements.org describes the rights status of cultural objects. Statements complement a provider’s detailed information; they do not license your own creations. These three codes have different meanings.

Digitised heritage: a rights statement is not a licence
ReferenceValue or formWhat it identifies
InC1.0Copyright or related rights apply; uses beyond those permitted by law require permission.
NoC-OKLR1.0No copyright restriction, but other known legal restrictions apply in some jurisdictions; read institutional details.
CNE1.0Copyright status has not been evaluated, not “public domain”.
rights URIStatement ≠ licenceKeep URI and version with the exact resource; a portal-wide notice does not replace object-level status.

Implication for the record

Identify whether the statement covers a reproduction, work, metadata or another resource. Preserve specific notices and reuse terms. For images or translations, check third-party information and intended use; a code is not universal permission.

Can CNE be simplified to “rights-free” in a caption?

No. That changes an unevaluated status into permission. Keep the published status and establish a reuse basis for your use. If that cannot be established, choose another resource with documented terms.

Primary documentation

Documentation consulted on .

DOCUMENTED REFERENCE

DataCite: distinguish license text, code and URI

Schema 4.7 describes rights without confusing a license name with its standardized identifier. These fields use JSON spelling; XML differs in places, for example rightsURI.

DataCite: distinguish license text, code and URI
ReferenceValue or formWhat it identifies
rightsList0…nRights information is optional and repeatable. Multiple entries can describe complex rights; absence grants no additional permission.
rightslicense titleReadable text identifies the license or rights statement. Retain its full title and version where provided.
rightsUriURIThe URI points to the license. Examine the actual link, not merely a word such as open in a description.
rightsIdentifierCC-BY-4.0CC-BY-4.0 is an example of a standardized identifier, not evidence that all DataCite resources use that license.
rightsIdentifierSchemeSPDXSPDX identifies the code system here, not the depositor or rights holder.
schemeUrihttps://spdx.org/licenses/The code-system URI points to the SPDX directory and differs from the specific license URI.

Implication for the record

DataCite Commons builds its license graph from rightsIdentifier. An unknown category can therefore mean this structured field is absent even when information exists elsewhere. Check the version and third-party material actually reused.

Is a DOI labelled unknown necessarily closed or unlicensed?

No. This is the state of metadata used for that representation. Read the record and resource, retaining the information and scope found; do not turn unknown into inferred permission or prohibition.

Primary documentation

Documentation consulted on .

DEEPER READING / PRACTICE

Find the conditions associated with the resource

A dataset is publicly accessible but its reuse conditions are not immediately visible. The verification must find the text or reference associated with the resource concerned.

Updated on .

Priority checks

Keep file, file, license mention, version and date of consultation. Discover the differences between the terms of the portal, the dataset and the built-in content.

Interpretation pitfalls

Accessibility does not demonstrate a general permission for reuse. A mention on a portal may not describe all the files or elements of the dataset.

Working record to retain

The license note collects relevant references and passages, and then lists the unresolved questions. The conclusions remain limited to the effectively documented conditions.