Data Modeling For Content Types (Postgres/Relational)
Budget: €30 – €250 EUR
Looking for individual who is experienced in data modeling (structure schema) for different types of content.
Also payment is negotiable and flexible - open to any time of arrangement (per day / per hour / per task / etc)
Familiar with:
Relation Types
CMS (conceptual)
SQL DBs (Postgres)
Schemas
Tasks Include:
Creating Schemas for Content Types you are given
Relating Content Types to Each Other
If you're familiar with working with APIs (then also seeding the DB Content)
And example of a modeling-task would be that you are given an example of a type of content concept - let's say posting to Facebook for this example. You will then reduce the example down into the inputs needed to create a Facebook post (think message body / image(s) / posting date / user / etc.).
For each modeling-task you will be given:
visual example of the content (if possible)
explanation of how the content may be used
how it is (or maybe in the future) be related to other types of content
Conceptual understanding the different relational types (e.g., Many-to-One (M2O) | One-to-Many (O2M) | Translations (O2M) | Many-to-Many (M2M) | Many-to-Any (M2A) | One-to-One (O2O)), along with concepts of junction tables/key value pairing/etc are a must.
The data modeling that you do will be for a Postgres based CMS designed using Vue / TS / NodeJS with both graphQL and REST APIs. You are not required to know those languages (it just may possibly make it easier for you).
Deliverables
Data models added to CMS and updatable via API
Also payment is negotiable and flexible - open to any time of arrangement (per day / per hour / per task / etc)
Familiar with:
Relation Types
CMS (conceptual)
SQL DBs (Postgres)
Schemas
Tasks Include:
Creating Schemas for Content Types you are given
Relating Content Types to Each Other
If you're familiar with working with APIs (then also seeding the DB Content)
And example of a modeling-task would be that you are given an example of a type of content concept - let's say posting to Facebook for this example. You will then reduce the example down into the inputs needed to create a Facebook post (think message body / image(s) / posting date / user / etc.).
For each modeling-task you will be given:
visual example of the content (if possible)
explanation of how the content may be used
how it is (or maybe in the future) be related to other types of content
Conceptual understanding the different relational types (e.g., Many-to-One (M2O) | One-to-Many (O2M) | Translations (O2M) | Many-to-Many (M2M) | Many-to-Any (M2A) | One-to-One (O2O)), along with concepts of junction tables/key value pairing/etc are a must.
The data modeling that you do will be for a Postgres based CMS designed using Vue / TS / NodeJS with both graphQL and REST APIs. You are not required to know those languages (it just may possibly make it easier for you).
Deliverables
Data models added to CMS and updatable via API