Open joaquimrcarvalho opened 1 year ago
Currently it is not possible to use abstract groups in part lists. Part lists need to enumerate the specific groups that can occur.
This prevents to higher level groups to define possible contained groups at an abstract level.
A good use case is the top level group kleio:
kleio
part name=kleio; also=structure,translator,autorels,obs,prefix,translations; position=structure,translator,obs; part=historical-source,fonte,authority-register, identifications
Note that we need to specify fonte and identifications even though they are specializations of historical-source and authority-register.
fonte
identifications
historical-source
authority-register
This could make it difficult to add new sources and register types in a multi file layout.
See updatePath(OldGroup,OldID,NewGroup,Path,NewPath):-
This is necessary to allow user defined new groups to be added easily, otherwise groups like "sources" and "fontes" have to be changed to integrate new types of acts.
Currently it is not possible to use abstract groups in part lists. Part lists need to enumerate the specific groups that can occur.
This prevents to higher level groups to define possible contained groups at an abstract level.
A good use case is the top level group
kleio
:Note that we need to specify
fonte
andidentifications
even though they are specializations ofhistorical-source
andauthority-register
.This could make it difficult to add new sources and register types in a multi file layout.