Skip to content

Api cleanup#113

Merged
alexdryden merged 24 commits intodevelopfrom
api-cleanup
Jan 28, 2023
Merged

Api cleanup#113
alexdryden merged 24 commits intodevelopfrom
api-cleanup

Conversation

@alexdryden
Copy link
Contributor

To help prepare for a more substantial API overhaul, this just cleans up some loose ends by adding appropriate messages to the REST API and refactoring functionality to work as expected

Adjust terms used because TeamResources use a composite
primary key instead of an incremented ID. It was also necessary
to turn off strict_trans_tables to avoid getting error:
"Expression #2 of SELECT list is not in GROUP BY clause and c
ontains nonaggregated column 'omeka_local.t0_.resource_id' which
is not functionally dependent on columns in GROUP BY clause;
this is incompatible with sql_mode=only_full_group_by". This may
require further attention.
Because team-resource is just a join table, no additional
information is stored for an individual entity, i.e. it is nothing
but the resource id and the team id. So, there is no point in a
single entity read opperation.
For search, this entity uses a composite key: team_id-resource_id,
so search requests must have one of those elements instead of an
entity id. Searching for a team will return all of its team
resources, search for a resource will return all of the teams it
belongs to.
While we consider which features whould be exposed to the API
@alexdryden alexdryden merged commit c8da17e into develop Jan 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant