[EdgeDB] Create Producible, Film, EthnoArt, and Story schemas

[bryanjnelson]

@CarsonF - I'm not necessarily sold on the splitting out of all of these into their own esdl files now that I see the end result. A case could be made to place them all in the producible.esdl. Or perhaps even include them in the Producible module even? Thoughts appreciated.

Monday Task

┆Issue is synchronized with this Monday item by Unito

[CarsonF]

I'm not necessarily sold on the splitting out of all of these into their own esdl files now that I see the end result. A case could be made to place them all in the producible.esdl. Or perhaps even include them in the Producible module even? Thoughts appreciated.

Yeah I could go either way. I'd probably lean towards one file. Idk about moving them all into the Producible module. That would be a non-trivial name change compared to app code, but I definitely like the idea. Just not sure about how much we should be deviating at this point...

Speaking of deviation though, I wonder if we should just make Producible extend Named. My thought years ago was to not enforce this field, as producibles could be labeled differently, e.g. film title vs something else. This hasn't exactly played out well though. They all have a single name field right now, so it's kinda silly we don't just have it on the producible.
That certainly makes it easier:

abstract type Producible extending Resource, Mixin::Named {
  overloaded name {
    delegated constraint exclusive;
  }
  scriptureReferences: multirange<int32>;
}
type EthnoArt extending Producible;
type Film extending Producible;
type Story extending Producible;

[bryanjnelson]

Speaking of deviation though, I wonder if we should just make Producible extend Named. My thought years ago was to not enforce this field, as producibles could be labeled differently, e.g. film title vs something else. This hasn't exactly played out well though. They all have a single name field right now, so it's kinda silly we don't just have it on the producible.
That certainly makes it easier:

abstract type Producible extending Resource, Mixin::Named {
overloaded name {
delegated constraint exclusive;
}
scriptureReferences: multirange;
}
type EthnoArt extending Producible;
type Film extending Producible;
type Story extending Producible;

Yeah, I was wondering if you were going to say something about that. I like it...and will make it so!