master ammunition table

[simra]

id: id -- record id caliber: string -- eg 20x102mm cartridge_type: string -- eg HEI-T (Self Destruct), M246 casing_material: string -- eg brass country: string -- eg United States. manufacturer: string year_start: int -- allow for year ranges with a start/end field year_end: int headstamp_markings: string projectile: string casing_description: string primer: string notes: text created_date: datetime created_by: id headstamp_image: id -- each will have exactly one canonical headstamp and profile image profile_image: id

[simra]

• [x] add table and ui to add/edit records
• [x] workflow for associating canonical images
• [ ] add ui to associate headstamp detections with ammunition record
• [x] add ui to browser records
• [x] workflow for profile images
• [x] "source" tracking. Decide whether to associate with a record or with an image.

[simra]

Bugs/items to address:

• [x] upload and render associated images
• [x] ammunition list page rendering doesn't display as list
• [x] editing year fields is broken
• [x] show usernames rather than ids?
• [x] css for ammunition edit view
• [ ] ammunition page cancel button doesn't reset state
• [ ] validate there can be only one reference collection?
• [x] validate reference images are in a public collection
• [ ] paginate the ammunition list

[simra]

@monkeypants, some questions to noodle on in relation to some of my recent pushes to branch https://github.com/Tech4Tracing/CartridgeOCR/tree/simra/ammo_table

• We have user-owned collections of images of mostly headstamps
• We have added a table of reference ammunition records (with lots of text descriptors). In principle one record per distinct identifiable cartridge type. These records should be public to all users and editable by only a subset of users (who? superusers? a pool of users with a special permission scope?)
• each ammunition record currently points to a canonical headstamp image id, and a canonical profile image id.
• do we want to enable ammunition records to point to multiple images for each type (eg multiple canonical headstamp shots)?
• We only have a mechanism to upload images to collections- do we use the same API to upload these images? If so, to what collection? How are these images special? How do we indicate these images are public, maybe without making the collection itself public?
• Do we need to add some additional image attributes (headstamp vs profile view?)
• would there ever be any reason to have multiple collections of reference ammunition records and image sets? Or One Collection to Rule Them All?

[simra]

consider allowing users to specify any collection they own as a reference collection? whether an ammunition record is editable should depend on their superuser status.