Skip to content

Releases: Indicia-Team/warehouse

v5.0.0

27 Feb 18:27
Compare
Choose a tag to compare
  • Dropped support for oAuth2 password authentication as no longer recommended in the oAuth 2.0
    Security Best Current Practice. See https://oauth.net/2/grant-types/password/.
  • JWT authentication on the REST API - dropped http://indicia.org.uk/alldata token in the payload.
    Now, default is to return user's own data only, but this can be expanded by specifying scope
    in the payload with a space separated list of scopes (sharing modes) - defining which website's
    records will appear in the response. Options include: userWithinWebsite, user (all records for
    user across all websites), reporting, verification, data_flow, editing, peer_review, moderation.
    If a JWT token claims multiple scopes, the URL parameter scope can select the active one for a
    request.
  • Adds occurrence custom attribute system functions for behaviour and reproductive_condition.

v4.11.0

19 Jan 17:12
Compare
Choose a tag to compare
  • New UKSI operations warehouse module which accepts a log of taxonomic updates in the same format
    as used to update the master copy of the UKSI taxon list. This reduces the need for periodic and
    complex full updates of the UKSI taxonomy.
  • New es_key_prefix option in application/config/indicia.php which allows a prefix to be added
    to IDs in Elasticsearch downloads (to uniquely ID the warehouse).
  • Support for Excel (*.xls or *.xlsx) files in the importer (experimental).
  • After upgrades, now more effectively clears appropriate parts of the cache so that UI and ORM
    updates are immediate.
  • Performance improvement by indexing notifications table for count of user's outstanding
    notifications.
  • Improvements to Elasticsearch download column templates, e.g. for better MapMate export support.
  • Option to skip overwrite of verified records in the Rest API sync module (e.g. for iNaturalist
    synchronisation), see BiologicalRecordsCentre/iRecord#972.

v4.10.0

17 Dec 17:26
Compare
Choose a tag to compare
  • New uksi_operations module allows update logs for UKSI to be directly imported, with support for
    new taxon, amend metadata, promote name, merge taxa, rename taxon operations.
  • Addition of organism_key to taxon table for improved links with UKSI.
  • Generation of taxon path data now more reliable (report filtering by higher taxa).
  • New work queue task for efficient updates of taxonomy related fields in occurrence cache tables.
  • Server status message on home page fixed immediately after install.
  • Minor tweaks to improve the install process.
  • Support for dynamic addition of termlist terms when inserting attribute values (tag style, e.g.
    using the data_entry_helper::sublist control).
  • Fix to check constraint for unique email addresses. Excludes deleted records.
  • Fixes a problem where importing to update existing records caused duplicates.
  • Elasticsearch downloads now support automatic inclusion of custom attributes for a survey.
  • Fix for importing anonymous records into Recorder 6 using Indicia2Recorder.

v4.5.0

16 Sep 13:56
Compare
Choose a tag to compare
  • Bugfix for saving an occurrence via the warehouse UI.
  • Refactoring of way entities are configured in the REST API.
  • REST API now supports creation of surveys, sample and occurrence attributes for users with site
    admin role.
  • Several bugfixes relating to RESTful API behaviour.
  • Support for creating DINTY tetrad references from server-side database code (e.g. in reports).

v4.4.0

21 Aug 15:46
Compare
Choose a tag to compare
  • The training flag can now be applied to samples, not just occurrences.
  • Add support for importing locations from SHP files in Web Mercator projection.
  • Importing a location with multiple entries in the SHP file *.dbf file now results in multiple
    locations, rather than only the first being imported. They can be manually merged afterwards if
    required.
  • Rest API supports JWT authentication, including support for storing a public key in website
    registration details that can be used for JWT authentication in the REST API.
  • Rest API supports creating, updating and reading samples, occurrences and locations. See
    /index.php/services/rest after upgrading the warehouse for details.
  • Rest API suports a media-queue endpoint which allows images to be posted first then attached to
    subsequent data submissions.
  • Submissions of any media data can include a queue field value instead of a path. If supplied,
    then a matching file will be copied from the media queue if it exists and linked to the
    submission.

v4.2.0

03 Aug 07:52
Compare
Choose a tag to compare
  • Attributes display additional info for termlists in lookup to help disambiguate similar names.
  • Addition of freshwater_flag, terrestrial_flag, non_native_flag to taxonomic data model.
  • Support for a new easy-download format in Elasticsearch downloads.
  • Summariser module integration with work queue.

v4.1.1

23 Jun 12:57
Compare
Choose a tag to compare
  • Fixes installation issues caused by incorrect module load order.

v4.0.8

16 Jun 13:47
Compare
Choose a tag to compare
  • Fixes installation issues in #347 and #348.
  • PHP 7.4 compatibility

v4.0.0

20 May 12:17
Compare
Choose a tag to compare

Major version update due to breaking changes in the Elasticsearch REST API:

  • Format for the addColumns parameter in calls to the Elasticsearch REST API
    endpoints (for CSV downloads) now changed to match the format of the client
    [dataGrid] control's columns configuration. Therefore custom ES download
    formats will need reconfiguring on the client.

  • PHP minimum version supported now 5.6.

v3.4.0

04 May 08:38
Compare
Choose a tag to compare
  • Ability to import into the locations table whilst referencing the
    location's parent by id.
  • Ability to import into the samples table whilst looking up the
    associated location by id.
  • If location ID provided when importing a sample, then the sample's
    entered_sref and entered_sref_system fields are not required in the
    import data as they can be extracted from the location.