...
| budgetingapplies | |
| usepriceschedule | |
| sendfeed | |
| hideskippedproducts | |
| shownonfullsupplytab | |
| enableskipperiod |
Facility
...
Program Product
Program Product ISA
Program Product Price
Facility
| id | |
| code | |
| name | |
| description | |
| geographiczoneid | |
| typeid | |
| catchmentpopulation | possibly might want to move this out to an extension |
| operatedbyid | |
| active | |
| golivedate | |
| godowndate | |
| comment | |
| enabled | |
| location | has location related attributes (mainphone, fax, address, lat, long, altitude, etc.) |
| createdby | |
| createddate | |
| modifiedby | |
| modifieddate | |
| implementations should handle these via attributes or json extradata field | |
| gln | |
| coldstoragegrosscapacity | |
| coldstoragenetcapacity | |
| online | |
| satellite | |
| pricescheduleid | |
| haselectricity | |
| haselectronicdar | |
| suppliesothers | |
| sdp | |
| haselectronicscc | this one should probably move into inventory management context |
| facility ftp details | |
facility_demographic_estimates; demography as another domain?
facility_mappings; support mapping to DHIS2 facility code somehow (ELMIS)
mos_adjustment_facilities, order_quantity_adjustment_products; ???
Facility Type
| id | |
| code | |
| name | |
| description | |
| displayorder | |
| active | |
| createddate | |
| createdby | |
| modifiedby | |
| modifieddate | |
| implementations should handle these via attributes or json extradata field | |
| nominalmaxmonth | |
| nominaleop | |
Note: consider an alternate model of facility capabilities, instead or in addition to facility type
Facility Operator
| id | |
| code | |
| name | |
| description | |
| displayorder | |
| createddate | |
| createdby | |
| modifiedby | |
| modifieddate |
Program Supported
| id | |
| facility | |
| program | |
| startdate | |
| active | |
| standard audit fields |
Processing Schedule
| id | |
| code | |
| name | |
| description | |
| standard audit fields |
Processing Period
| id | |
| processingSchedule | |
| name | |
| description | |
| startdate | |
| enddate | |
| numberofmonths | is this needed? |
| standard audit fields |
TODO: Get rid of period short name and include as a field in Processing Period?
Is this a sub-resource of Processing Schedule?
Hierarchy and Supervision
Supervisory Node
TODO: consider along with other things that deal with hierarchy and supervision
Requisition Groups and Members
Supply Lines
User
| id | |
| username | |
| password | |
| firstname | |
| lastname | |
| restrictlogin | does this duplicate active? |
| primarynotificationmethod | consider pulling all notification into its own domain |
| officephone | consider pulling all notification into its own domain |
| cellphone | consider pulling all notification into its own domain |
| consider pulling all notification into its own domain | |
| supervisorid | |
| facilityid | |
| verified | |
| active | |
| preferences | user-specific preference settings |
| implementations should handle these via attributes or json extradata field | |
| employeeid | |
| jobtitle | |
| ismobileuser | |
user_password_reset_tokens
"Product" (Requestable)
Open Questions
Can we merge fulfillment_role_assignments into role_assignments?
View file name tableNotes.xlsx height 250
...