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

File metadata vs Grants metadata #301

Open
mariongalley opened this issue Jun 16, 2021 · 4 comments
Open

File metadata vs Grants metadata #301

mariongalley opened this issue Jun 16, 2021 · 4 comments

Comments

@mariongalley
Copy link
Contributor

Need to think about how we communicate the difference between these two types of metadata. @KDuerden @mrshll1001

@KDuerden
Copy link
Contributor

It would be useful to understand more about this
What prompted this issue?
What are examples of file metadata?
What are examples of grant metadata?
Where does the communication about the difference need to go? Is this primarily about the metadata guidance in the docs site. Anywhere else?

@mariongalley
Copy link
Contributor Author

mariongalley commented Jun 21, 2021

@robredpath had some thoughts on this, namely that the metadata extension exists to talk about file metadata, but there are other places that talk about the grants data and potentially use the word metadata to talk about it (not sure if I remembered our discussion correctly?)

@robredpath
Copy link
Contributor

robredpath commented Jun 22, 2021

This came out of the dashboard work - in the wider 360Giving world, we talk about "metadata" to mean both the grant-level metadata fields (Last Modified, Data Source), the new package-level metadata (the "meta sheet"), and occasionally, the data that we derive from the published data (aggregates, etc).

We don't talk about the grant-level metadata as being metadata in the standard, right now - but we do talk about the package-level metadata as being metadata. In the existing dashboard, we call grant-level metadata just "metadata", and don't track package-level metadata.

We don't currently track either type on the new dashboard, but we may well want to in the future. In any case, we probably do want to track adoption of the new package-level metadata, and having a clear way of communicating what we're talking about is important - as "metadata" is ambiguous, now.

@KDuerden
Copy link
Contributor

thanks @robredpath
I'm drafting the 'how to' guidance for the package metadata, so it would be great to get your feedback on that once it's ready - see how we can start making these distinctions clear and develop consistent language.

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

No branches or pull requests

3 participants