One of the digital archivists tried to wrtie the syntax is("value1","value2") rather than is("value1") or is("value2"). Obviously this doesn't work currently, but as it was actually using an ExplicitContextExpr too(ie referring to the value of another column) it made for a much more compact expression, so this might be worth considering for later versions of the schema language.
One of the digital archivists tried to wrtie the syntax is("value1","value2") rather than is("value1") or is("value2"). Obviously this doesn't work currently, but as it was actually using an ExplicitContextExpr too(ie referring to the value of another column) it made for a much more compact expression, so this might be worth considering for later versions of the schema language.