[ANSWERED] Question re: Multi-Thread Projects

[Drace]

So I'm really active posting threads for cleaning up multiple editions of a book in the Projects folder, and something of an ongoing project I've been posting is making threads to clean up books published by a particular horror imprint. So far, I've just been posting one thread at a time, but it's kind of slow going (I'm doing the books in order of release, and the current thread I have going is for a book published in 2021). So I wanted to get some librarian input on best practices here. Should I:

1. Keep going with one thread at a time in chronological order like I have been doing?
2. Switch to a two threads at a time model: one thread for a book that's already been released, and one thread for an upcoming book? When an already-released book thread finishes I'd start a new one for another already-released book, and when an upcoming book thread finishes I'd start a new one for the next book on their release calendar.

I feel like switching to Option 2 might be a better way to cover more ground and work with librarians to ensure that new books aren't going neglected, but I'm open to other opinions on this.

[gem]

In the past when I've worked on your projects, if I see "updates needed for new book releasing soon" or similar in the post title, I prioritized that project over others. Not sure if that answers your question.

Also thanks for your ongoing work in researching and consolidating data for book updates. Have you ever considered applying to be a Librarian?

[Drace]

Thanks for your help. I think for now Option 2 might be the best option to take, but only making a new thread when the publisher's next book is getting close to release.

I actually previously passed the librarian test and was a librarian for a week or two, but I realized that working on my master's (and my job as a real-life librarian) would keep me busy and I wouldn't be able to work much on Goodreads edits, so I asked for my status to be taken away and made edits to a few books on my shelves while I waited for that to happen. I might apply again in the future, but I'm still pretty busy with IRL stuff for the moment.

[Martin]

I would have thought that making edits yourself would be quicker and simpler than writing detailed requests and responding to librarians questions.

[Drace]

Martin wrote: "I would have thought that making edits yourself would be quicker and simpler than writing detailed requests and responding to librarians questions."

Maybe, but staying on top of all the other requests people make would be the biggest issue for my schedule.

[Arenda]

There is no requirement to answer requests in the Librarians Group. There are many librarians just working on their own books (or projects).

[Tami]

Just to add to what Arenda said. There's no need to cover a quota of edits per month or anything like that. If you are busy and can't edit books, no problem; there's no need to give up your librarian status. They don't take away your librarian rights if you are inactive. I know librarians who don't edit a lot—it's just a few edits every few years, and they are still librarians.

[L J]

I read posts in Librarians Group to keep up with policy changes and so on when I don't have time to do much. For instance now I'm occupied with yard work beyond what I would usually do at this time of year because I have cooperation of new neighbor. The project may take several more weeks but when I'm back to having time I'll know what is going on.

[Drace]

Thanks for the input, everyone. I might try to apply for librarian again later this summer when I have more time.

[Liralen]

Just want to agree with what others have said—sometimes there's more time to work on librarian requests than others. (You know when I have more time to work on librarian things because I'm in your threads :-P) I might go a long stretch of time without dipping into the requests in this group, and that's fine; I'm still able to fix things as I come across them.