2018-05-15 Meeting notes
Date
May 15, 2018
7am PST / 4pm CET
Meeting Link
Note we're using Zoom now:
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/737202874
Or iPhone one-tap :
US: +16699006833,,737202874# or +14086380968,,737202874#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 669 900 6833 or +1 408 638 0968 or +1 646 876 9923
Meeting ID: 737 202 874
International numbers available: https://zoom.us/zoomconference?m=F0kj5u6u0wFxr7Xfz5NKZxl0xyLhuTPF
Attendees
@Josh Zamor (Deactivated)
Goals
See discussion items
Discussion items
Time | Item | Who | Notes |
|---|---|---|---|
10m | Agenda and action item review |
| Open action items from last time: @Paweł Albecki (Deactivated): take the feedback from the DDD and package name improvements and show through a diagram and/or use of the example service what it'd look like given that feedback https://openlmis.atlassian.net/wiki/spaces/OP/pages/214466562/DDD+and+package+name+improvements |
| From Showcase on May 9, 2018 the following were brought up to discuss in TC or decide on the dev forum
| @Craig Appl (Unlicensed) @Clay Crosby (Unlicensed) |
|
| Stock Reason tagging | @Sebastian Brudziński, @Chongsun Ahn (Unlicensed) |
|
(for next time) |
| @Craig Appl (Unlicensed) |
|
(for next time) | UI - Table approach after https://openlmis.atlassian.net/browse/OLMIS-4541 | @Nikodem Graczewski (Unlicensed) |
|
(for next time) | Cross-service migration | @Chongsun Ahn (Unlicensed) |
|
(for next time) | API Designs for Stock Based Requistions (or for review) | @Sebastian Brudziński |
|
(for next time) | Demo data - review new findings | @Chongsun Ahn (Unlicensed) |
|
Notes
API Reporting Review
Is it valuable to transition?
Who can
What skills are needed?
How to get the points in red out of wiki into work to be done?
One is to big, how to right-size it
Some might reflect that a more restful approach would be appropriate
Wiki page: APIs Tech Debt review
Reporting Platform Repo Structure
Josh had lots of questions... Craig and Josh will meet: sidecar, structure of each image, is it generic, etc
Chongsun asked about generic-ness of Nifi repo. Could we have only one Nifi for multiple uses: reporting and demo data loading
Stock Reason Tagging
Does MJ have a concern about current tagging concept? Something in Logistimo about user and system tagging?
Technical concerns?
I did followup with @Mary Jo Kochendorfer (Deactivated) on Stock Reason Tagging and I don't think we should be expanding the scope:
don't enforce business logic on which tags may be assigned to which reasons - that's categorization
don't require that a reason have a tag - again categorization
I don't think we need system and user tags - sounds again like categorization but I might misunderstand.
Overall the difference between tagging and categorization doesn't have a hard definition that I know of, however from the DAM and CMS software I've used the best definition I can think of quickly is that tagging includes the concept of categorization - they both add context to a thing. However in categorization you divide the world. A photo can be categorized by the date it was taken because one photo can never be taken on two different days. On the other hand a photo could be tagged with different colors which might overlap, e.g. it might have been tagged green and red because the photo had both green colors and red colors in it, as well as every color in the spectrum between the two. Tags add context, categories add context but divide the world into separate buckets. Stock Reasons already have a category.
The main concern is how to explain to an implementer how to implement a useful tagging system, which isn't easy and their are books written on the subject. I think however a user-oriented message will be mostly sufficient. Twitter hashtags are a parallel that might help us explain to end-users these concepts.
We can discuss further in the technical discussion that's later this week.