ksobon
commented
4 years ago @gschleusner1972 well, I guess the big picture question here is this: Do we have a requirement for each object to be fully self describing? The reason I am asking is before, we didn't have that requirement. As a matter of fact, I think it was opposite. We talked about specifically not putting additional information into these individual RFI files, because their location would give us context. Literally their location on a hard drive determined what was the project that they belonged to etc.
This changes that requirement, and now each RFI will contain full reference to the project. Same with RFI responses, that will contain full reference to the RFI. We can do that, but then the question is, what's the benefit of doing that?
From the description above it seems you want to be able to share RFI Responses via Email. That's running counter to the idea that we would use GDrive/Box/Resilio to manage these. There is no need to email anything if it gets shared automatically via gdrive. It's the person's adding a response responsibility to add it to the right folder, rather than the receiver's to know what folder the response was intended for. Why are we changing this approach?
gschleusner1972
If you think about these files as transactions you need more data then just the details on each element to ensure that they can act alone without other details being included. IE. If I send you one of these files via email would it have enough information so that you would not have to intervene to ensure it goes to the right location? With that in mind, we'd need to add the following to the RFI, Response data and then Add the ProjectUUID to the project. Also I think we need to create a json descriptor of the attachements tht have a matching name with this same info.
ProjectUUID ParentUUID - (for Responses to RFIs and future item types) PredisesorUUID - (This is used for responses. The responses should be ordered so a second response's "PredisesorUUID" would be the "ItemUUID" of the first responce, , where the ParentUUID for the second responce is the "ITtemUUID" of the RFI itself.
ItemUUID - All elements would have this. UTC Timestamp ItemType (RFI,RFIComment,RFIAttachment)
{ "Number": "002", "Contractor": { "Name": "Konrad's Contracting" }, "ContractorRfiNumber": "005", "Subject": "Just testing another", "ReceivedDate": "2020-09-21T15:21:38.1960914Z", "DueDate": "2020-09-28T15:21:38.1960914Z", "Details": "This concept would work well for a host of design related data types. Issues. Schedule. Even a slow chat app.", "Attachments": [] }