Accession order in trait data
We usually rely on seqNo + id
for accession order in Genesys. When fetching trait data from Amphibian, we send the UUIDs of all accessions to consider, and Amphibian handles the pagination.
Browsing trait data across different datasets shows accessions are not ordered:
- The accession UUIDs in
AccessionService#getAccessionUuids(AccessionFilter filters)
must be orderedseqNo asc, id asc
- Amphibian needs to respect the order of incoming UUIDs (we now use
Set<>
which does not guarantee order) - I'm not sure if we can easily fix the order of accessions in single datasets because we don't have
seqNo
norid
in Amphibian.