decisions need to be made here about whether a "parentWork" is a mandatory or optional field
a work is identical to a workGroup except that it can only take expressions as children, while workGroup can take other workGroups, works, or expressions as direct children.
In many cases a work only has one expression as thus the relationship is one to one and feels burdensome to record.
However there are many cases where a work is need to categorize expressions, like Wodeham's Ordinatio and Abbreviatio. Without a concept of work and a canonicalExpression, full text search results could become filled with redundancies. It will be ideal to have a way to filter out non-canonicalExpressions.
Pros and Cons: Making a parent work "optional" creates complications when writing queries. Making a parent work group "required" creates an extra layer that can often feel redundant.
Right now the project file has a field for parentWorkGroup.
But if a parentWork is stated, the parentWorkGroup should be inferred from the description of the work not the expression, and therefore the field should be removed.
if parentWork is option, the EDF file will need to support both a parentWorkGroup and parentWork field.
decisions need to be made here about whether a "parentWork" is a mandatory or optional field
Right now the project file has a field for parentWorkGroup.
But if a parentWork is stated, the parentWorkGroup should be inferred from the description of the work not the expression, and therefore the field should be removed.
if parentWork is option, the EDF file will need to support both a parentWorkGroup and parentWork field.