Adding more updates and revamping updates page

Author: Renato Juaçaba Neto

_posts/2024-11-12-updates-to-sparql-endpoint.md

@@ -5,6 +5,8 @@ description: You may now query all registry metadata directly on our SPARQL endp
 categories: updates
 ---
 
+# SPARQL and RDF improvements
+
 Thanks to ELIXIR's BioHackathon 2024, we could use [project 13](https://github.com/elixir-europe/biohackathon-projects-2024/blob/main/13.md) to improve our sparql endpoint with data from our registry. Special thank you to Jerven Bolleman and all the DBCLS team for all the help in this achievement and the ELIXIR BioHackathon organization team.
 
 Registry data was modeled based on the DCAT and VoID RDF schemes in addition to additional terms for all registry data. You will find all the information that you need to use it in our [sparql documentation page](/pages/sparql) 

_posts/2025-03-25-automated-registry-validation-is-back-online.md

@@ -0,0 +1,19 @@
+---
+layout: default
+title: Automated registry validation is revamped and is back online
+description: Issues with URLs and metadata is now automatically flagged with our curator team
+categories: updates
+---
+
+# Improved automation of the registry data
+
+Based on the [iaso validation and curaton tool](https://github.com/identifiers-org/cmd-iaso) we have created the validator component and curation warning system.
+
+The curation warning system is a way for authorized actors to post warnings to our registry to be handled by our curators.
+The system is able to track multiple types of warnings, repeated warnings for the same problem, and maintain a history of events on a warning.
+
+With the curation warnings in place, our validator cloud hosted recurring process that runs modular validators on our registry dataset and generates multiple curation warnings. These are then posted to registry to be curated by our team.
+
+Please have a look at [our source code](https://github.com/identifiers-org/monorepo/tree/810d600d2ead91649849e43a824d61b1d5730522/webservices/validator-registry) for the available validators and warning types.
+
+If you wish to contribute with validators or wish to join by generating curation warnings. [Please get in touch with us](/pages/contact).

_posts/2025-04-10-registry-data-repository.md

@@ -0,0 +1,42 @@
+---
+layout: default
+title: Registry data is now also available in a GitHub Repository
+description: Find the registry data via git in our new public repository
+categories: updates
+---
+
+# Registry data on GitHub
+
+In an effort to provide an additional backup and a versioned version our registry data, we have set up a self updating GitHub repository which checks, downloads, and versions itself based on our live resolver dataset endpoint.
+
+The repository can be found at <https://github.com/identifiers-org/registry-data>.
+
+### Data files
+All the data is available in the [registry-data](https://github.com/identifiers-org/registry-data/tree/0397a5cfccf98019103da625d171caf9d02faf8e/registry-data/) folder. 
+They are stored in the same JSON schema available at our live endpoint.
+The file [full.js](https://github.com/identifiers-org/registry-data/tree/0397a5cfccf98019103da625d171caf9d02faf8e//registry-data/full.json) contains the full dump of the registry. 
+The dump is also available split by namespace under the [registry-data/namespaces](https://github.com/identifiers-org/registry-data/tree/0397a5cfccf98019103da625d171caf9d02faf8e/registry-data/namespaces/) folder.
+
+### Versioning
+The current version of the repository is found at the file called [VERSION](https://github.com/identifiers-org/registry-data/tree/0397a5cfccf98019103da625d171caf9d02faf8e//VERSION) at the root of the repository.
+The commit history can be used to check recent changes to the identifiers.org registry.
+
+#### Checking history via Github.com UI
+
+Recent changes to the dataset can be seen in the [commit history of full.json](https://github.com/identifiers-org/registry-data/commits/0397a5cfccf98019103da625d171caf9d02faf8e/registry-data/full.json). 
+You will have to click on individual commits to see its changes.
+
+Alternatively, recent changes to an individual namespace can be seen in the commit history of the specific namespace file, for example, [the commit history for 3dmet can be found here](https://github.com/identifiers-org/registry-data/commits/0397a5cfccf98019103da625d171caf9d02faf8e/registry-data/namespaces/3dmet.json). 
+Again, You will have to click on individual commits to see its changes.
+
+#### Checking history via git command line
+
+After cloning the repository and opening a terminal there, you can list recent changes to the dataset using the following command:
+```shell
+git log --patch -10 registry-data/ 
+```
+
+The similar command below can be used to see changes on a specific namespace file:
+```shell
+git log --patch -10 registry-data/namespaces/3dmet.json 
+```

_posts/2025-09-18-url-convergion-api.md

@@ -0,0 +1,27 @@
+---
+layout: default
+title: "New feature: Provider URL conversion API"
+description: We are now able to help users convert provider URLs into identifiers.org URIs
+categories: updates
+---
+
+# New URL convertion UI
+
+Due to the difficulty a lot of users have when first trying to use identifiers.org, we have developer a new way to convert providers URLs into identifiers.org URIs. A new search bar is available on our front page where users can input provider URLs and get our stable identifiers.org URIs.
+
+![](/static/img/convert-url-screenshot.png)
+{:.border}
+
+Exact matches will display immediately, as shown above. When one is not available, a link will take you to a page like show below where we offer a search by similarity which tries to find the best results for the URL given.
+
+![](/static/img/convert-url-screenshot2.png)
+{:.border}
+
+
+### New API endpoints
+
+This UI is powered by our resolver API backend which can also be used directly. Please find documentation on the methods at our [API documentation page]({% link pages/api.md %}).
+
+### Improvements and suggestions
+
+If you think of any improvements or have any suggestions to this feature, please [get in touch with us](/pages/contact).

_posts/2025-10-02-new-way-to-use-idorg-features.md

@@ -0,0 +1,36 @@
+---
+layout: default
+title: New ways to use our resolution services!
+description: New addon, widgets, and MCP functionality
+categories: updates
+---
+
+# New ways to use our resolution services
+
+Thanks to the recent [DBCLS BioHackathon 2025](https://2025.biohackathon.org/) we are able to offer a few ways to facilitate access to identifiers.org in many new ways.
+
+### MCP server
+
+The [Model Context Protocol (MCP)](https://modelcontextprotocol.io) provides the definitions to facilitate the interaction of systems with AI agents. 
+Now, our users can integrate identifiers.org into their AI-powered workloads by connecting to our resolver API using MCP.
+With this, users may request AI models to resolve CURIEs and/or generate identifiers.org URIs for their data.
+
+To access our MCP endpoints, set up an SSE connection to <http://resolver.api.identifiers.org/sse>. There you will find the tools and prompts specifications. To inspect the functionalities, use the [MCP inspector](https://modelcontextprotocol.io/docs/tools/inspector) or your favorite AI app or agent with support to MCP integration.
+
+
+### Browser extension
+
+If you use our services frequently, please consider installing our browser extension on Firefox (with a Chrome version being on the way).
+With this you are able to quickly resolve CURIEs and convert provider URLs using the embedded search bars or the right click actions. Please find more information in the add on marketplace at <https://addons.mozilla.org/en-GB/firefox/addon/identifiers-org>.
+
+
+### Widgets
+
+Based on the [togostanza widget framework](http://togostanza.org/), we offer developers the opportunity to integrate identifiers.org into their websites. The widgets can be found at <https://docs.identifiers.org/togostanza-widgets/> in addition to examples and usage instructions.
+
+Three widgets are available:
+- One is the resolution bar from our front page in case you wish to help users input curies into their pages;
+- Another is a button to convert URLs and copy the equivalent identifeirs.org URI into the users clipboard
+- The last is a text wrapper to validate and resolve CURIE identifiers.
+
+

_posts/_UPDATES_TEMPLATE.md

@@ -2,7 +2,7 @@
 layout: default
 title: TITLE TO SHOW ON UPDATES LIST
 description: EXTRA TEXT SHOWN ON UPDATES LIST
-categories: updates THIS IS IMPORTANT
+categories: updates THIS_IS_IMPORTANT_BUT_REMOVE_THIS
 ---
 
 FULL DESCRIPTION OF UPDATES SHOULD BE SHOWN HERE

index.html

@@ -35,12 +35,13 @@ <h2><i class="icon icon-common icon-documentation mr-2"></i>Identifiers.org docu
 		This web page contains resources to help users and developers working with the platform.
 		We will continue adding information here as we expand and document the services.
 		For recent updates, check <a href="/pages/updates">our list of updates</a>.
-		If you can't find what you are looking for, feel free to <a href="pages/contact">contact us</a>.
+		If you can't find what you are looking for, feel free to <a href="/pages/contact">contact us</a>.
 	</p>
 
 	We have kept things as backwards compatible as possible in the platform,
 	but there has been some changes from the previous version.
-	If you are interested in a detailed list of differences, please take a look at the
+	If you are interested in a detailed list of differences, 
+	please take a look at <a href="/pages/migration">our migrating instructions</a>.
 
 	<hr>
 

pages/api.md

@@ -67,6 +67,7 @@ Refer to the example for more details.
     }
   ```
   - ↪ The accession attribute is optional. When undefined, the resolver will guess it based on the URL components.
+  -       [See the source code for more details](https://github.com/identifiers-org/monorepo/blob/810d600d2ead91649849e43a824d61b1d5730522/webservices/resolver/src/main/java/org/identifiers/cloud/ws/resolver/services/reverseresolution/ReverseResolutionService.java#L68-L85).
   {: .list-none}
 - **Response body example:**
   ```json
@@ -102,7 +103,8 @@ Refer to the example for more details.
         }
     }
   ```
-  - ↪ The accession attribute is optional. When undefined, the resolver will guess it based on the URL components.
+  - ↪ The accession attribute is optional. When undefined, the resolver will guess it based on the URL components. 
+  -       [See the source code for more details](https://github.com/identifiers-org/monorepo/blob/810d600d2ead91649849e43a824d61b1d5730522/webservices/resolver/src/main/java/org/identifiers/cloud/ws/resolver/services/reverseresolution/ReverseResolutionService.java#L68-L85).
   {: .list-none}
 - **Response body example:**
   ```json

pages/updates.md

@@ -4,17 +4,26 @@ title: updates page
 ---
 
 <h1> 
-    identifiers.org updates
+    Our latest updates
     <a href="/static/updates.rss">
         <img class="updates-rss" src="/static/img/rss.png" />
     </a>
 </h1>
 
-<ul>
+<ul id="update-list">
   {% for post in site.categories.updates %}
-    <li>
-      <a href="{{ post.url }}"> {{ post.title }}</a>
-      <p> {{ post.description }} </p>
+    <li class="update-item">
+      <div class="update-date">
+        {{ post.date | date_to_string: "ordinal", "US" }}
+      </div>
+      <div class="timeline-circle"></div>
+      <div class="update-title">
+        <a href="{{ post.url }}"> {{ post.title }}</a>
+      </div>
+      <div class="timeline-line"></div>
+      <div class="update-description">
+        {{ post.description }}
+      </div>
     </li>
   {% endfor %}
 </ul>

static/css/styles.css

@@ -414,3 +414,45 @@ hr {
 .language-sparql .ss {
   color: rgb(160, 0, 160);
 }
+
+#update-list {
+  display: grid;
+  grid-template-columns: auto auto auto;
+  width: fit-content;
+  gap: 0 1rem;
+  padding-top: 1rem;
+}
+
+#update-list .update-item {
+  display: contents;
+}
+
+#update-list .update-item .update-date {
+  text-align: end;
+  font-size: 110%;
+}
+
+#update-list .update-item .update-title {
+  font-size: 110%;
+}
+
+#update-list .update-item .update-description {
+  grid-column: 3;
+  padding-bottom: 2rem;
+}
+
+#update-list .update-item .timeline-circle {
+  border-radius: 50%;
+  background-color: darkorange;
+  border: 1px solid rgb(130, 130, 130);
+  width: .9rem;
+  height: .9rem;
+  margin-top: 50%;
+  margin-left: .05rem;
+}
+
+#update-list .update-item .timeline-line {
+  grid-column: 2;
+  width: 1rem;
+  background: linear-gradient(rgb(130, 130, 130), rgb(130, 130, 130)) no-repeat center/2px 100%;
+}