Document ROR lookup support when creating institutions and projects

[Copilot]

ROR-backed institution search was added to SEEK but the user guides for creating institutions and projects did not explain how to use it.

• Documentation updates
  • Add guidance to the admin “Creating institutions” page on using the ROR search, auto-populating details, entering a known ROR ID, and proceeding manually when no ROR entry exists.
  • Add equivalent guidance to the project creation flow when defining an institution during project setup.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/seek4science/seek-documentation/pages
  • Triggering command: /usr/bin/ruby3.2 ruby3.2 /tmp/bundle/ruby/3.2.0/bin/jekyll build --gdwarf-5 --64 -o pipe.o /tmp/ccJkHsv5.s -I kward -I y-3.2.0 -I by-3.2.0 -I kward -I y-3.2.0 -I as (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

#51
supporting ROR are added at two places

1. create an insititute
2. create an project
   add some documentations for this new feature.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[whomingbird]

add an enriched, clearer version based on the copilot generated text with screenshots.

[PhilReedData]

Hi @whomingbird, I've changed/added a few things. I'm happy to merge now.

• Image links need to be wrapped in a little Liquid code to ensure they show for SEEK & DataHub docs, since the pages can be served from the root or from a directory.
• Added a bit of motivation why to include ROR when creating an institution.
• Used our seek_instance.name variable in several places (for DataHub docs).
• Used the ETT proper Note block syntax.

[PhilReedData]

Sadly, our Markdown renderer considers an ordered list to start from 1 every time there is an image (or similar) break between items. So I wrote the numbers out as words.