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

[Proposal] Add details to source attributes #261

Open
matamadio opened this issue Oct 12, 2023 · 2 comments
Open

[Proposal] Add details to source attributes #261

matamadio opened this issue Oct 12, 2023 · 2 comments
Labels
proposal New feature or request

Comments

@matamadio
Copy link
Contributor

What is the context or reason for the change?

The source attributes include name, url, type and component.

What is your proposed change?

A description field to add details about the source would be useful, especially to explain the relationship between the source and the dataset in object.

E.g. "the source dataset/model has been clipped for the geographic region / resampled to different resolution / reprojected on a different CRS / etc.)

@matamadio matamadio added the proposal New feature or request label Oct 12, 2023
@matamadio matamadio changed the title [Proposal] [Proposal] Details of source Oct 12, 2023
@matamadio matamadio changed the title [Proposal] Details of source [Proposal] Add details to source attributes Oct 12, 2023
@stufraser1
Copy link
Member

This could also allow us to describe how the source data has been used in the analysis.
I learned yesterday that Meteor data uses ISO fields lineage > processStep to describe the steps taken in the analysis, in that case for preparing exposure dataset.
Example: LSO_oed_exposure_20200811.xml.zip
Lineage starts at ln683, with a list of biblio references (which RDLS separates into individual sources)
The first of seven processSteps start at ln759

We could use either description field, or an additional field dedicated to describing the use of that source?

@matamadio
Copy link
Contributor Author

We can have just "Description" to hold all content, or "Description" and "Lineage" as separate fields, where lineage specifies any change from the source.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal New feature or request
Projects
Status: Under discussion
Development

No branches or pull requests

2 participants