|
You had a complex data gap that you fixed. Library Browser issue was a symptom.
No need to ever do a straight 1-22. Just have to avoid creating a gap. If things get totally confused, however, that is a good way to reset to a valid sequence before saving, restarting, then changing to the desired sequence. No need to live with a straight 1-22.
Path is a required column, since it is used internally in several places (e.g. read a book, save a copy, get the book ID, etc). Cannot be optional.
Good idea about the specific CC label in the slot.
My current project is a new plugin, Entities Manager. An entity may have many links and many notes. Associated entities point to their unifying entity that has their links and notes to avoid duplication. Example: Pseudonyms point to the real author that has the links and notes. Or not. Flexible. Associations are optional.
Entity = (type + value) where type is the metadata column name (standard or custom) and value is a metadata value. Any Entity can be associated with any other Entity with no regard to type.
Numeric and composite custom columns are not valid Entity Types.
Author, Series and Publisher are the standard column valid types.
As many links and notes per entity as desired.
Book ID not involved at all. Library-level.
January 2019 beta release.
DaltonST
|