add rors

[NicolasCARPi]

elabftw/elabftw#6949
:)

Summary by CodeRabbit

• Documentation
  • Added new FAIR data documentation covering persistent identifiers, ORCID profile configuration and automatic assignment, organizational identifier associations, and support for the .eln format for exporting and importing research data.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 344b7921-1c4e-4e00-a450-464f91a22f73

📥 Commits

Reviewing files that changed from the base of the PR and between 4f36ba0 and 408ec7f.

📒 Files selected for processing (2)

• docs/usage/fair.md
• static/img/fair-ror.webp

---

📝 Walkthrough

Walkthrough

A new documentation page docs/usage/fair.md has been added, covering FAIR (Findable, Accessible, Interoperable, Reusable) aspects in eLabFTW. It documents eLabID format, ORCID configuration (manual and SAML-based since v5.6), ROR associations at instance/team/user levels, and .eln file interoperability via the RO-Crate format.

Changes

FAIR Documentation Page

Layer / File(s)	Summary
FAIR documentation page: metadata, overview, identifiers, and interoperability docs/usage/fair.md	New page with frontmatter metadata, a FAIR principles introduction, a Persistent Identifiers section documenting eLabID format, ORCID manual and SAML/IdP automatic assignment, ROR at instance/team/user levels with an interface image, and .eln RO-Crate-based interoperability linked to the Import/Export page.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

Ensign, set a course for FAIR compliance, warp factor documentation! 🖖
eLabIDs stand immutable, like stardate logs in the archive,
ORCID beams in through the SAML relay,
ROR holds position at instance, team, and crew.
The .eln format — our universal translator — carries data true.
Number One's log: all systems nominal, FAIR and away! 🚀

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'add rors' is vague and does not clearly convey the actual scope of changes, which involve comprehensive FAIR documentation covering persistent identifiers, ORCID configuration, ROR associations, and ELN formats.	Consider revising the title to be more descriptive, such as 'Add FAIR data documentation covering persistent identifiers and ROR integration' or similar, to better reflect the actual content of the documentation page.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}