You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For organisation of all lists I'd like to suggest a file structure as follows:
"[$PUBLISHER] ($YEAR) List Name [Part #XX] (Source)"
With this information lists can easily by organised in a folder using name ordering.
YEAR - Start year of the arc. This will help users keep lists sorted chronologically. We'll need to think up how to quantify the start year since you want to exclude extremities from that. Perhaps the first issue of the core series if there is one?
List Name - Matched against CV name if possible
Part #XX - For lists >100 issues long, split into parts of max 100 issues. For string sorting I think it's best to use double digits everywhere (eg. #3, #8, or #13)
Source - Include where the list was generated from. At the minute these are CV, CBRO, CMRO and Manual. We'll need to number the manual lists somehow to distinguish multiple (if there are multiple).
The text was updated successfully, but these errors were encountered:
For organisation of all lists I'd like to suggest a file structure as follows:
"[$PUBLISHER] ($YEAR) List Name [Part #XX] (Source)"
With this information lists can easily by organised in a folder using name ordering.
YEAR - Start year of the arc. This will help users keep lists sorted chronologically. We'll need to think up how to quantify the start year since you want to exclude extremities from that. Perhaps the first issue of the core series if there is one?
List Name - Matched against CV name if possible
Part #XX - For lists >100 issues long, split into parts of max 100 issues. For string sorting I think it's best to use double digits everywhere (eg. #3, #8, or #13)
Source - Include where the list was generated from. At the minute these are CV, CBRO, CMRO and Manual. We'll need to number the manual lists somehow to distinguish multiple (if there are multiple).
The text was updated successfully, but these errors were encountered: