Open fosterlynn opened 9 years ago
As a start, here are the data elements involved: 1) Non-Sensorica use: This would be a Sale (exchange and a shipment/delivery event). The service is use of the printer in hours. Data needed: --Printer (can hardcode the new printer if we want) --Service of using the printer (can hardcode this too) (note we want to implement a way for those two resources to know about each other - "underlying resource") --Project (can hardcode this if we want) --Date (default today) --# of hours --Person using the printer (customer) --Value (can calculate from hours * price of the service if it is always the same)
2) Sensorica project use: This would be an input Use event to an existing process. Means the process must be planned ahead of time. --Commitment (choose from those with printer use planned) (or possibly need to choose an existing process active during the time period if the commitment doesn't exist) --Date (default today) --# of hours --Person using the printer (from agent)
If there is no process, then the person would need to create a process and the use event.
Another possible connection - do we want to log use of polymer inputs at the same time?
From discussion with Tibi:
See https://docs.google.com/document/d/1U5NTRUHna6vYnv6riKyUrl8Xn8kn2K7ShrzaBy_ZyUM/pub#h.6crht2pallw0 for current access rules.
Everyone needs to log hours and consumables. Perhaps pick use case (e.g. commercial, project, co-owner, etc.)? Need to know who. Can log for others. Choices: Anyone with an agent resource relationship to the resource (like custodian, owner, manager), exchange firm(s), fablab members, techshop members. Doesn't it also need to be any affiliate?
Also, Tibi will create a barcode for the URL for the printer. (A separate one for each piece of equipment logged in this way.) We can embed info in the URL, e.g. resource id, project id. The user can scan the code into a smartphone, which will access the URL.
We will create a separate Django app for this, accessing the existing data.
From more discussion with Tibi: -May need a choice of scenario and different paths, if support all the logging needed. -Dropdown should not be any affiliate (see question above). -Try to include logging payment to a technician. -Try to trigger the distribution. Or at least report in a way making it easy to enter for now. -Add how paid (the box, paypal, the little square thingy).
We think there might be two different use cases: 1) Sensorica projects that may eventually pay for their printer use through sales of products or services, and 2) non-Sensorica projects that will pay for their printer use pretty much immediately.
It is possible also that people who contributed to the printer will have free time on the printer, need to double check the agreement.
Feedback has been solicited from Sensorica.