How should we handle metadata fields?

opensupplyhub / supplychaindata.exchange

supplychaindata.exchange.schema

Creative Commons Zero v1.0 Universal

4 stars 2 forks source link

How should we handle metadata fields? #7

Closed shuyag closed 3 weeks ago

shuyag commented 1 month ago

Alongside the data fields within the core schema, how should we consider metadata? Likely to need to include:

time of creation, updating, deletion (or perhaps archiving, to keep a record)
provenance of data

The second layer of complexity to consider here include:

deletion for a duplicate record or mistake, with an update to correct
updating a record because of change in location active status
accounts or verification needed for provenance, would this be for verification, and/or coming back to understand contributions and fixes

shuyag commented 1 month ago

Re: provenance, how could one handle being able to get in contact with verification of a data set? Or would the "directory" of getting in touch with the contributor actually live separately from the standard?

We might consider the verification/source of data being something that sits within the unique IDs.

For any locations though, we might be able to have a more frequent updating of active/status for locations than the IDs are able to update. Is it worth adding a data attribute field for "status"?

shuyag commented 3 weeks ago

Merging this issue with another one around metadata fields: https://github.com/opensupplyhub/supplychaindata.exchange/issues/2