Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Evaluate approach how specific location can have their dedicated description/assets #74

Open
santilland opened this issue Dec 19, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@santilland
Copy link
Collaborator

Looking at indicator E9 of trilateral, each location has a dedicated markdown file.
In principle i think we could "just" provide a new description for the item and have a generic for the collection, but we need to evaluate how we can configure this so it is injected during generation of the items.
In the E9 case it would be for geodb data.

@santilland santilland added the enhancement New feature or request label Dec 19, 2023
@lubojr
Copy link
Member

lubojr commented Dec 19, 2023

I would assume this falls under homogenization of the metadata on a per-collection level. I don't think we should have to implement this on location level?

@santilland
Copy link
Collaborator Author

Good point, as next steps we discussed cleaning the description markdown files to be data descriptive and not have "stories" within. So it is possible this would no longer be needed then.
Let's keep this issue open and collect this points to discuss them in our next "data migration" session.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants