Centralised List Approach #10
jakem742
started this conversation in
Reading Lists
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
#7 got me thinking about what could possibly be a neat way to manage lists in a way that is super easy to maintain, update and edit over time.
If we can add Event, Character and Team tags to each individual book in the CBL file, we can (in theory) have ALL the info needed to create any event/character/team list in a single master CBL file. Partial files could then be created from the master file using a script we supply to the users. Any time there is an update to the lists, they simply update their master list and regenerate the partial files using the script we supply. This way each user can selectively generate whichever partial character/event lists they want at their leisure.
All we would need to do is link certain issuesID's with Characters, Events and Teams in the backend db, and then we could regenerate the CBL file as many times as needed with no extra work.
Beta Was this translation helpful? Give feedback.
All reactions