You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When importing data into the datastore we store the field order from the source, however, if we don't have any of these details (say, for example, the data was sideloaded directly into mongo and elaticsearch) then we just use the fields from the resource's index mapping in elasticsearch. These fields are ordered alphabetically to maintain some level of consistency.
It'd be nice to allow implementors of the IVersionedDatastore interface to reorder the fields, perhaps:
This comes off the back of NaturalHistoryMuseum/ckanpackager#47.
When importing data into the datastore we store the field order from the source, however, if we don't have any of these details (say, for example, the data was sideloaded directly into mongo and elaticsearch) then we just use the fields from the resource's index mapping in elasticsearch. These fields are ordered alphabetically to maintain some level of consistency.
It'd be nice to allow implementors of the
IVersionedDatastore
interface to reorder the fields, perhaps:This allows the implementor to both override the field order and change the fields if they want.
The text was updated successfully, but these errors were encountered: