TODO: PT and GT should discuss this before proceeding. May be best achieved with a JSON schema change.
Promote metadata fields that we want users to access via API, and don't share metadata.
I.e, promote: date, rights, schema, creators, language, publisher, pages, isbn.
Reason: "metadata" can contain data not really meant for users to see. Examples:
- detailed tag data (not very problematic)
"source_tags" (if present) lists tags from the resource itself.
"tagger_data" is actual data form the Climate Tagger API.
- internal storage location info (problematic)
"content_download_link" right now can point to private S3 resources, e.g., "content_download_link": "s3://knowledge.commons/island_press/9781610915991.epub"
TODO: PT and GT should discuss this before proceeding. May be best achieved with a JSON schema change.
Promote metadata fields that we want users to access via API, and don't share metadata.
I.e, promote: date, rights, schema, creators, language, publisher, pages, isbn.
Reason: "metadata" can contain data not really meant for users to see. Examples:
"source_tags" (if present) lists tags from the resource itself.
"tagger_data" is actual data form the Climate Tagger API.
"content_download_link" right now can point to private S3 resources, e.g., "content_download_link": "s3://knowledge.commons/island_press/9781610915991.epub"