Doco - review searchable fields

[f27wood]

I was looking for doco on how somebody would identify if an object is on display and what gallery it is in, and could not find this info. I think it just needs to be added to the searchable fields in the getting started guide?

So adding this issue to review that part of the guide as there are probably other fields not included as they did not exist when it was first written.

[Conal-Tuohy]

See the note in https://github.com/NationalMuseumAustralia/Collection-API/wiki/Getting-started#beta-release-known-issues and review.

[Conal-Tuohy]

• [x] acknowledgement
• [x] additionalType
• [x] aggregates_object_id
• [x] collection
• [x] collection_id
• [x] contentDescription
• [x] contributor
• [x] contributor_id
• [x] creator
• [x] creator_id
• [x] datestamp
• [x] depth
• [x] description
• [x] diameter
• [x] educationalSignificance
• [x] gender
• [x] geo
• [x] hash
• [x] hasPart_narrative_id
• [x] hasPart_object_id
• [x] height
• [x] id
• [x] identifier
• [x] isAggregatedBy_narrative_id
• [x] isPartOf_narrative_id
• [x] isPartOf_object_id
• [x] issued
• [ ] issued_date
• [x] length
• [x] location
• [x] media
• [x] media_id
• [x] media_object_id
• [x] medium
• [x] modified
• [ ] modified_date
• [x] name
• [x] physicalDescription
• [x] reason
• [x] related_object_id
• [x] rights
• [x] seeAlso
• [x] significanceStatement
• [x] source
• [x] source_count
• [x] spatial
• [ ] spatial_geo
• [x] spatial_id
• [x] status_code
• [x] temporal
• [ ] temporal_date
• [x] text
• [x] title
• [x] type
• [x] unitText
• [x] unitTextWeight
• [x] weight
• [ ] width

[Conal-Tuohy]

Leave out id, hash (for internal use only) and reason, since it adds nothing to status_code, which is documented.

[Conal-Tuohy]

sourceCount is another for internal use only (part of the incremental update accounting mechanism)

[Conal-Tuohy]

type is also not for use as a search field; it is part of the "path" component of query URLs, e.g. object, media, etc.

[Conal-Tuohy]

Remaining issues the _date fields, the spatial_geo field, and the various unpopulated dimension fields. I will raise these as separate issues and close off this issue.