DRAFT: Implement metadata schema in Django & PostgreSQL

[NEStock]

Changes

• Re-organized backend structure (see below for details)
• Definitions for Project, Contributor, and Funding classes
  • based on LinkML schema - https://github.com/aplbrain/BBQS-EMBER-Data-Model/blob/main/EMBER_Metadata/schema/ember_project_metadata.yaml

Notes

Backend Organization

(note: not all files are shown, just depicting the general structure)

backend/
├── apps/                     # Container for all Django domain apps
│   ├── core/                 # Core domain: (placeholder) Shared, cross-cutting code
│   └── projects/             # Project domain: EmberProject, Contributor, Funding, relations
│       ├── migrations/
│       ├── models/
│       │   ├── contributor.py
│       │   ├── funding.py
│       │   └── project.py
│       ├── admin.py
│       ├── apps.py
│       ├── urls.py
│       └── views.py
├── config/                   # Django project configuration (settings + URL wiring)
├── main.py
├── manage.py
├── README.md

LinkML Schema

Unfortunately, while LinkML currently has generators for Python and SQL tables, it doesn't explicitly have one for Django, so I used the Pydantic generator as a "base" or guide for each class and then modified the fields from Pydantic to Django by hand (i.e. str -> models.CharField())

[netlify]

✅ Deploy Preview for emberarchive ready!

Name	Link
🔨 Latest commit	bc3bc5e
🔍 Latest deploy log	https://app.netlify.com/projects/emberarchive/deploys/695d39041028aa0009505ddc
😎 Deploy Preview	https://deploy-preview-97--emberarchive.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.