Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tag Index Roadmap #263

Open
braxtonhall opened this issue Jan 14, 2023 · 0 comments
Open

Tag Index Roadmap #263

braxtonhall opened this issue Jan 14, 2023 · 0 comments

Comments

@braxtonhall
Copy link
Owner

braxtonhall commented Jan 14, 2023

Supposed we implement the following:

Then the Tag Index can be explored/manipulated almost entirely in the extension itself, and we'd have license to change the Tag Index entirely

Let's imagine what a perfect Tag sheet looks like

image

This is basically a language.

Keywords

#comment

Means this row should not exist. Pretend this row is not here.

#sheet

Must be the first row of the sheet. This tells Better LibraryThing that the sheet is in fact a sheet that has been properly formatted and will include tags.

#description

Description of the sheet

It has the added benefit of having a name (in case you want it to be different from the Sheet name) and a description

#map | NAME | MAPPER | DESCRIPTION?

For mapped tags. You can have as many of these as you want.

#begin

This must be the last keyword used, and indicates the beginning of tags. Any cell beneath this one will be read as a tag, even if prefixed with # (except for #comment). No cells above this one will be read as a tag.

Additionally, the row immediately following that isn't a #comment will be ignored, and assumed a header

The sheet from beneath this point follows: CW, Description, Tag 1, Tag 2, ... Tag N

Because there is no data right of the tags, the tag tree can now be INFINITE!! Subsubsubsubsubsubsubsubtags baybeeee

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant