Releases: hubmapconsortium/entity-api
Releases · hubmapconsortium/entity-api
v2.3.10
- Support
group_uuid
and group_name
for Collections
- Disable multi-revision feature
v2.3.9
- Efficiency improvements with using
indexed:
flag variable to replace the search-api json mapping file
- Add constraint to allow only one set of "Multi-Assay Split" component datasets
v2.3.8
Simple Neo4j query tuning for read triggers
v2.3.7
- Synchronize Component Dataset status value with associated Primary Multi-Assay Dataset
- New features oriented to improve index procedure efficiency, exposed via
GET /documents/<id>
- Require members from the same group to update an existing entity via the PUT call
- Minor fix to an old typo
Full Changelog: v2.3.6...v2.3.7
v2.3.6
- Support new status
Incomplete
for Dataset/Publication/Upload
- Add two attributes to track existing component datasets after conversion to Multi-Assay Split
Full Changelog: v2.3.5...v2.3.6
v2.3.5
- Support hubmap_id in
GET /entities/<id>/instanceof/<type>
- Strip whitespaces around entity id to avoid 500 error
Full Changelog: v2.3.4...v2.3.5
v2.3.4
Implement a generalized subclass schema yaml inheritance
v2.3.3
- Two new endpoints
GET /datasets/<id>/donors
and GET /datasets/<id>/samples
to support full prov metadata
- Remove restrictions on the how many component datasets can be generated during multi-assay split
v2.3.2
- New endpoint
GET /entities/<id>/tuplets
- Rename
GET /siblings<id>
to GET /entities/<id>/siblings
with skipping extra triggers
v2.3.1
Add validator to prevent the Component datasets generated by Multi-Assay Split and Processed datasets generated by Central Process to be edited with different direct ancestors.