Repository navigation
Replies: 4 comments 9 replies
|
fwiw, the recently added bulk "Add tags" could handle your Split use-case: go to a view that has the combined tag, select all, add the new Suspense tag, then merge the "Thriller + Suspense" into "Thriller". |
|
Yes, this would be welcome, and the write-up of what your 187 books actually looked like is the useful part. One thing to line up before you build: #2438 asks for the same map from the other end, an admin-managed table of "incoming tag → canonical tag(s) or drop" applied on ingest and metadata fetch, plus an "apply now" pass over the library. Your page is that "apply now" pass with a preview in front of it. If both use one stored map, a cleanup you review once also keeps new books clean, which covers the "keep the map" point. So I'd shape it as:
@magdalar's bulk "Add tags" route works for a one-off split; the page earns its keep when there are dozens of them. If you'd like to put up the PR, go ahead. Starting with the map, preview and apply is a good-sized first piece, and I'll review it there. |
|
The map, preview and apply part is up as #2668, against #2438 as you suggested. It keeps one stored map, so the ingest and fetch follow-up can read the same rules, and the "only allow existing tags" option can sit on top of it as opt-in. I ran it on my own library for a few days before sending it. Next I'd like to let the existing Tags page drive it: a rename or delete there (by an admin) would also record the rule, so the map mostly builds itself from clean-up people already do. |
|
Thanks @new-usemame, that makes sense, and I agree a rule from the Tags page should be a visible choice rather than a side effect. I'm building the follow-ups now on top of #2668 and running them on my own library, so they're ready to go up one at a time once #2668 is through:
Happy to reorder or fold any of these together if that suits the review better. Wasn't sure if I should reply here or the PR so hopefully this gets seen by those doing the review as well. |
Uh oh!
There was an error while loading. Please reload this page.
I just cleaned up the tags in my own library (187 books), and wanted to ask whether a bulk version of it would be welcome in NextGen before building anything.
The tags had piled up from different metadata sources: Thriller, Thrillers, "Fiction / Thrillers" and "Fiction.Suspense & Thriller" side by side, five spellings of Fantasy on one book, Spanish tags from one source (Novela, Policial, Ciencia ficción), BISAC codes like FIC030000, names split at a comma ("Manhattan (New York" plus "N.Y.)"), placeholders like General / None / Unknown, and one spam tag. 184 tags, which went down to 108.
The Tags view from #1368 (thanks @new-usemame, and @magdalar for asking for it in #973) already does the per-tag part: rename, merge on a name clash, delete. What I ended up needing on top of that was:
I did it outside the app with a small script and a JSON map. In NextGen it could be a "Clean up tags" page built on your existing rename/merge/delete, plus split, with the preview and an apply button. The map could be exported/imported so people can share starting points.
Would that be welcome, or would you rather keep tag management to the per-tag view? Happy to put up a PR if you want it, or leave the idea here if it's not a fit.
All reactions