In order to efficiently load country-specific data into OpenLMIS, Malawi’s implementation team created the openlmis-refdata-seed tool. Because this was prior to the existence OpenLMIS’ stock management service, the tool didn’t include support for data which resides within it.
Because Angola’s implementation of OpenLMIS will use stock management from the get-go, it would likely be useful to add support for stock-related configuration to the tool. This would potentially include support for:
- Valid Sources/Destinations
User management has also continued to evolve since the initial creation of the openlmis-refdata-seed tool. Adding a user now requires the creation of configuration within multiple services, and the refdata-seed tool’s current support for user-creation is therefore insufficient.
For these reasons, I suggest that we start thinking of the utility more generically as the “data” rather than “refdata” seed tool. With that in mind, would the Core team be amenable to:
Pull-requests which fix user-creation, even though doing so involves services other than ref-data.
Pull-requests which add support for StockAdjustmentReasons and valid sources/destinations within stock-management.
Perhaps generalizing the tool’s name.
I imagine the first two of the above changes would be innocuous. I understand that JSI is building a UI for the tool, though, and don’t have a sense of whether tweaking its name would meaningfully effect them.