Skip to content

Conversation

@stephenkilbourn
Copy link
Contributor

@stephenkilbourn stephenkilbourn commented Sep 30, 2025

this is one of the tasks for issue #252 "Documentation to support external collection indexing"

Description

This adds documentation for indexing external data using titler-cmr. It provides the GPM_3IMERGDF example json config as an example

It also adds the instructions for ArcGIS

@github-actions
Copy link

github-actions bot commented Sep 30, 2025

PR Preview Action v1.6.2

🚀 View preview at
https://NASA-IMPACT.github.io/veda-docs/pr-preview/pr-255/

Built to branch gh-pages at 2025-10-10 16:13 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

@anayeaye
Copy link
Collaborator

anayeaye commented Oct 7, 2025

@stephenkilbourn sorry for the delay here--the content is looking good but I am having trouble navigating to it in the preview (this may be a result of the project structure more than the PR--there seems to be a lot of material that requires digging to find).

@stephenkilbourn
Copy link
Contributor Author

@stephenkilbourn sorry for the delay here--the content is looking good but I am having trouble navigating to it in the preview (this may be a result of the project structure more than the PR--there seems to be a lot of material that requires digging to find).

@anayeaye - this should be working in the preview now. Everything is starting from the "External Collection Indexing" page

https://docs.openveda.cloud/pr-preview/pr-255/user-guide/content-curation/external-collection-indexing/

@stephenkilbourn stephenkilbourn changed the title add Titiler-CMR to external collection indexing docs add Titiler-CMR and ArcGIS to external collection indexing docs Oct 10, 2025
@sandrahoang686
Copy link
Contributor

Do we need to include the publishing process as well in the end with either the ingest UI/keycloak or opening a pull request to veda-data? cc @anayeaye @stephenkilbourn

@anayeaye
Copy link
Collaborator

@sandrahoang686

Do we need to include the publishing process as well in the end with either the ingest UI/keycloak or opening a pull request to veda-data?

I think we probably should just focus on the how to create metadata here and then we will direct all cases back to a consolidated publish step. I'm sure there are cases that won't perfectly fit that but in general I would think we want to maintain a single authoritative ingest-ui document. 🤔
cc: @stephenkilbourn @smohiudd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants