Add Series Entry to Collection Objects

[alesan99]

Fixes #6276

Adds Bulk Carry Forward Range preference to Collection Objects.

Checklist

• Self-review the PR after opening it to make sure the changes look good and
  self-explanatory (or properly documented)
• Add relevant issue to release milestone
• Add pr to documentation list
• Add automated tests
• Add a reverse migration if a migration is present in the PR

Testing instructions

• Go to Data Entry for Collection Object
• Click on Form Meta and enable Carry Forward and Bulk Carry Forward Range. Also enable "create record set"
• Fill out some fields on the form and save.
• The Carry Forward range input should appear
• Make sure you can only enter a valid start catalog number (It should use the catalog num of the CO you just saved)
• Make sure you can only enter a valid end catalog number
• Make sure you can't enter invalid ranges (where the start is bigger than the end for example)
• Click Carry Forward and make sure all the COs in the range you specified were created
• Try to Carry Forward over catalog numbers belonging to COs that already exist
• Click Carry Forward and see a dialog with a list of all existing catalog numbers.
• Click on Form Meta and disable the "create record set on bulk carry" preference
• Try Bulk Carry Forward and make sure no record set is created. But make sure all newly created records appear on the form page thing.
• Try creating a CO with a Collection Object Type with that uses a different formatter for the catalog number. Bulk Carry should still work, except if the formatter does not support autoincrementing (the button will be disabled).

[alesan99]

TODO:

• Use bulk carry forward: Add a pref to use range instead of current incrementing behavior
• If range pref true, use the bulk carry forward box to enter the last cat num for the range
• Dialog for showing existing COs with catalog numbers
• Check if catalog nums are formatted correctly on frontend
• Check if catalog num range is correct on front end
• Option to disable record set creation
• Tests for series_autonumber_range
• Try to move range_end next to the catalog number on the form (if possible?). (Did this on a separate PR Add series entry field to form (series=true) #6871)
• Possible bug with formatter.title? Should use a new formatter.name property

[bhumikaguptaa]

• The Carry Forward range input should appear
• Make sure you can only enter a valid start catalog number (It should use the catalog num of the CO you just saved)
• Make sure you can only enter a valid end catalog number
• Make sure you can't enter invalid ranges (where the start is bigger than the end for example)
• Click Carry Forward and make sure all the COs in the range you specified were created
• Click Carry Forward and see a dialog with a list of all existing catalog numbers.
• Try Bulk Carry Forward and make sure no record set is created. But make sure all newly created records appear on the form page thing.

Works as expected!

[alesan99]

I fixed an issue with the catalog number formatter not being used if you are using one that has a custom title for it.

I added the following check to the instructions to test formatters:

• Try creating a CO with a Collection Object Type with that uses a different formatter for the catalog number. Bulk Carry should still work, except if the formatter does not support autoincrementing (the button will be disabled).

[emenslin]

Does not work on DBs with multiple collections (ojsmnh in the fossil inverts collection), but worked fine on a db with only one collection (kubirds). On a a DB with multiple collections it claims that the numbers are already being used when they do not exist, this is likely because the numbers do exist in another collection.

07-02_09.10.mp4

[alesan99]

@emenslin I think I have a fix for that, pushed it 👍👍

[emenslin]

• The Carry Forward range input should appear
• Make sure you can only enter a valid start catalog number (It should use the catalog num of the CO you just saved)
• Make sure you can only enter a valid end catalog number
• Make sure you can't enter invalid ranges (where the start is bigger than the end for example)
• Click Carry Forward and make sure all the COs in the range you specified were created
• Click Carry Forward and see a dialog with a list of all existing catalog numbers.
• Try Bulk Carry Forward and make sure no record set is created. But make sure all newly created records appear on the form page thing.
• Try creating a CO with a Collection Object Type with that uses a different formatter for the catalog number. Bulk Carry should still work, except if the formatter does not support autoincrementing (the button will be disabled).

---

I think if someone tries to carry forward over the range limit then it should just be blocked instead of throwing an error (something similar to the dialog when you try to carry forward over a number that already exists). With the current behavior the error also forces the user to go to the home screen which is not ideal.

07-03_14.41.mp4

[alesan99]

@emenslin I added a better dialog 👍 And if an error occurs for whatever reason you should be able to dismiss it now!

I did have to refactor parts of the code, so I could've broken some things. From my testing everything still seems to work, but you'll probably want to double check.

[emenslin]

• The Carry Forward range input should appear
• Make sure you can only enter a valid start catalog number (It should use the catalog num of the CO you just saved)
• Make sure you can only enter a valid end catalog number
• Make sure you can't enter invalid ranges (where the start is bigger than the end for example)
• Click Carry Forward and make sure all the COs in the range you specified were created
• Click Carry Forward and see a dialog with a list of all existing catalog numbers.
• Try Bulk Carry Forward and make sure no record set is created. But make sure all newly created records appear on the form page thing.
• Try creating a CO with a Collection Object Type with that uses a different formatter for the catalog number. Bulk Carry should still work, except if the formatter does not support autoincrementing (the button will be disabled).

Looks good, I did not run into any errors!