Add PlantUML processing and example #3219
Conversation
|
This is now ready for review/merge. It ended up with:
|
awwaiid
changed the title
|
Sorry I haven't gotten to this yet -- it feels like something I should look at when I'm fresh! |
doc/architecture/overview.md
Outdated
|
|
||
| ### Intake | ||
|
|
||
| A Diaperbank will acquire inventory primarily through one of two methods: a **Donation** or a **Purchase**. Purchases are straightforward; the Diaperbank spends its own money to purchase inventory. Donations can be received through a few different means. |
There was a problem hiding this comment.
Terminology note: We've gone almost entirely away from diaper-specific terminology. So it should be Essentialsbank, Productdrive
There was a problem hiding this comment.
I went through and switched most of the Diaper references to Essentials
| **Diaperdrives** are like food drives -- a campaign, typically with advertisement to the community, for the general public to provide needed items to the diaperbank. Sometimes people will also donate inventory at a local **Donation Site**, outside of a Diaperdrive. Other than those two primary methods, there is a miscellaneous classification for diapers that are received (but not purchased) through other means. | ||
|
|
||
| Donations can also dropped off at **Donation Sites**. These are locations that have been designated as places where people can drop off donations. | ||
|
|
| Sometimes, the diaper banks will need to make a correction, this application calls them **Adjustment**s. | ||
|
|
||
| When a diaper bank wants to move inventory from one storage location to another, they do so with a **Transfer**. | ||
|
|
| 3. Prompt the user to create a new barcode record using this value | ||
|
|
||
| For the second item, after the `BaseItem` is retrieved, it consults back to the Organization and finds the oldest `Item` (for that organization) that uses the retrieved `BaseItem`. | ||
|
|
There was a problem hiding this comment.
I love that we've got this kind of detail on barcodes somewhere.
If we've got this much detail at an overview level, though, we should also include kits
Or maybe break it up into more pieces
|
@awwaiid We'll also want to put something into the README to direct people to this. |
|
Consider adding |
|
I think I've addressed most of the feedback. If it looks tolerable for a draft then I'd like to merge it. As part of preparing for RFG-2023 I will submit further PRs for README cleanups which will link to this. |
|
No objections. |
Experimental in-tree generated diagrams