Allow for a specific value to be selected/added multiple times when picking properties where the hierarchy row with that value as object_uuid has '9' in 'custom' column
See below for rationale.
Note -- this is only useful with the value has more variables below it that will be saved with a different configuration than the first instance of that specific value.
Behavior - on front end, something like a '+' next to that value will allow for the user to add another value (and the variables below it) to the item_properties table.
This means that multiple branches of the same value will exist in item properties. (The primary example right now is for bibliography, see below).
Example: Text 1 is referenced by book A, article B, a chapter in an edited book (C), article D, and then book E references it in eight different places.
Text 1 will have 1 Bibliography tree with 5 "bibliographic reference" branches underneath it - one for each book A, article B, the chapter C, article D, and book E. In each tree, the publication (book/article/chapter) will be designated as to how it refers to the text (by 'Reference Type'), identified by the 'Referred work' variable (a link with a bibliogrpahy_uuid), possible noted about an improvement in line numbering ('Improvement from publication'), and given the beginning and ending page that the text was referenced on ('Reference location').
--In the case of book E where it references the text eight times -- that tree will have 5 'Referred location' branches.
Due to the way we construct property creation and selection on the front end (using hierarchy_uuid as a key) this is very difficult to implement). Review for other ways that contruct this situation?
Allow for a specific value to be selected/added multiple times when picking properties where the hierarchy row with that value as object_uuid has '9' in 'custom' column See below for rationale. Note -- this is only useful with the value has more variables below it that will be saved with a different configuration than the first instance of that specific value. Behavior - on front end, something like a '+' next to that value will allow for the user to add another value (and the variables below it) to the item_properties table.
This means that multiple branches of the same value will exist in item properties. (The primary example right now is for bibliography, see below).
Example: Text 1 is referenced by book A, article B, a chapter in an edited book (C), article D, and then book E references it in eight different places. Text 1 will have 1 Bibliography tree with 5 "bibliographic reference" branches underneath it - one for each book A, article B, the chapter C, article D, and book E. In each tree, the publication (book/article/chapter) will be designated as to how it refers to the text (by 'Reference Type'), identified by the 'Referred work' variable (a link with a bibliogrpahy_uuid), possible noted about an improvement in line numbering ('Improvement from publication'), and given the beginning and ending page that the text was referenced on ('Reference location'). --In the case of book E where it references the text eight times -- that tree will have 5 'Referred location' branches.
Example of what this would look like in item_properties (mocked up in a google sheet): Go here for the sheet itself (with a few notes): https://docs.google.com/spreadsheets/d/1ROoMbYApAWC-nEsiFDF_wFLpdTSlqadbGqpzdtwHVd0/edit#gid=874391749