-
Notifications
You must be signed in to change notification settings - Fork 0
Description
I just added 147 new identifications in the bulkloader. All had identification_order = 1, existing_order_change = +1. All new identifications were added to records successfully, with order of 1. In most cases the increment of the identification order worked exactly as desired. However, if there had previously been two identifications, one with order 1 (the good one), and another with order 0 (a depreciated or erroneous one), the +1 increment created a problem: the erroneous identification now has order of 1, and the good one now has order of two, with the new identification also having a (clashing) order of 1.
Can we please slightly modify this behavior of existing_order_change = +1 in the bulkloader?:
- Prior order of >= 1, increment order by one.
- Prior order of 0, leave as 0.
The info table at https://arctos.database.museum/loaders/BulkloadIdentification.cfm?action=ld would become:
Plus sign and integer, example "+1": Increment existing identifications to their current value plus one, with a ceiling of 10, except for existing identifications of order zero, which will remain zero.