Define Postgres Schema

[qjhart]

FWIW, I started playing around with a postgres schema for bibframe data. Not sure if this comports at all w/ sinopia's existing backend organization. Feel free to add issues there if you have any questions, but it's very unpolished right now.

[qjhart]

@sfolsom I think alot of the postgres schema must depend on how it will drop into the sinopia framework so @jermnelson will have a better understanding, but here are my questions:

Prototype

Are there different tables for works/Instances etc?

Are we using postgres postgres inheritance to combine those?

Are components required for simple search (eg. Title) pulled into their own columns for each item

• Is that '@en' centric?

Are other components (like LC vocabs) stored as their own resource(s)

• The metadata team seemed to indicate that we should be very accepting (one particular example, having a resource like above, but with a different label should be allowed) How is that managed

Are sinopia templates included or will they be managed in a different schema/server?

Are versions (like in sinopia ) included in the database.

Will resources be standardized (like labels non-blank nodes, included or not or either)

MVP

How do we cluster for better performance with many items