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
Create a CanonicalItem type that will be replicated into Item on Org creation
Create a method that automates the replication (no overwrites, but no direct duplicates) -- [ ] If possible, integrate existing Item records to work with CanonicalItem
~~~- [ ] Make the "key" be programmatically generated and idempotent.~~~
- [x] Administrative users can manage `CanonicalItem`s, normal users cannot see those CRUD tasks
- [x] Regular users can maintain their own `Item`s, adding, modifying, deleting, etc, but any `Item` they add must root in a `CanonicalItem` (N.B. care should be taken when deleting an item that has previously been used by `Donation`, `Distribution`, etc)
- [x] Add a way to "hide" an Item when it's requested to be deleted but has prior history
- [x] Refactor "size" into a field, instead of just being in the name (so it can be filtered, etc)
## Changes to BarcodeItem
- [x] Global `BarcodeItem`s are rooted with `CanonicalItem`
- [x] Local `BarcodeItem`s are rooted with `Item`
- [x] `BarcodeItem` link to `Item` is polymorphic
## Workflow for new organization signup
1. New org signs up
2. Canonical items are replicated into regular items for the org
3. Org then does whatever kind of modifications they want to those items (full CRUD), adds more, deletes any that have never held inventory, etc.
The text was updated successfully, but these errors were encountered:
TODO: Add scopes to display CanonicalItem types that have been created in last 30 days and are not currently among the item types of the current user. Display those as a notification to the signed-in user so they can opt-in if they want.
Changes to Item
Use separate tables, not STI
CanonicalItem
type that will be replicated intoItem
on Org creation-- [ ] If possible, integrate existingItem
records to work withCanonicalItem
The text was updated successfully, but these errors were encountered: