API - Data Model

[arlentees]

Create a starter data model for the doc api database for use in standing up the MVP/proof of concept document service. Base the document types on the analysis document: https://docs.google.com/document/d/1T0G5kTh78ewycgGRHBMiYqUwTBBpbE-b/edit

• Create DDL scripts for creating/dropping the database objects.
• Stand up a local instance.
• Stand up a DEV instance in the GCP BCR Common Dev project.

[doug-lovett]

@cameron-eyds moving your repo question to here: To follow up on the brainstorming/pre-grooming we just had, would we store documentId -> documents as a one to many relationship? Seemed like there is something there to ponder, if there isn't a consolidated pdf until the point of archiving.

My answer: Yes, that is my takeawy, there is no unique constraint on the document Id associated with a document. So in the UI if multiple documents belong to the same document ID, and the API is generating the document ID, then the UI would submit the documents one at a time, and the doc ID would be in the response for the first document id, and the subsequent requests would include that document ID. Or the UI zips the documents and we store them together (I don't think that will fly).

[cameron-eyds]

@doug-lovett Copy that, yea that makes sense to me!

I'm curious about the current work flow with regards how supporting documentation is associated to the documentId they assign and consume as part of a filing.