A little while back I floated the idea of a Journals Project
which would monitor journals and update Wikitree as new articles come in. I have been ruminating a little on how it might be implemented.
First things first: is "Journals Project" a good name? Is "journals" a good G2G tag to flag posts related to the project? That's what I'm going with, but I'm open to change.
It seems to me comments on G2G posts are more efficient than just having a slew of comments on the right side of a project page, so I propose for now that the main communication about the project will occur through G2G. Perhaps later a Google Group or Discord Channel or something could be setup.
There needs to be a way to divide articles among participants so as to avoid duplication, and there need to be some initial guidelines for how Wikitree is updated. My initial thoughts:
Anyone joining the project can pick journals that interest him/her. Many people will gravitate toward the American "big five", so it should be no problem getting at least several of those covered. Participants should make sure there are quality freespace source pages for the journals being monitored, including background information and a source citation that is easy to copy-and-paste.
What to do when a new issue comes out?
I have been thinking that when a new issue of a monitored journal comes out, there will be an initial sketch of issue information, like a fancy table of contents. So for instance, a new TAG issue would get a freespace page linked to from the main TAG source page. Initially just a table of contents or the like would be put on the freespace page, and people could claim articles on the page. If project participants identify individual profiles on Wikitree that are covered in the issue, they could create links on the issue page to make those profiles easy to find.
I think articles that are a source dump, e.g., a list of marriages performed by some minister, will be extremely hard to get into Wikitree, so we should skip those. These records often have no context, and IMO it is a bad idea to create a profile based on a single source, the way FamilySearch does (I guess with bots?)
Most other articles are family sketches. When I had first floated the idea for the project, I thought it would get a little bit of attention and be small. Perhaps that is still the case. With a small number of participants, there is probably no hope to completely update Wikitree with information from the family sketch articles, creating profiles and linking them as needed. My thought was instead that on each issue freespace page, the principal people in each article would be identified. A search would then be made to find these profiles on Wikitree and to add the new articles in the sources sections. This would be the minimal goal. People would feel free to update bios or link/create profiles as time permits.
Besides the initial project setup, with which I would welcome any kind of help, it seems to me that project roles will specialize into two sorts. Initially, some folks will need to process new issue information, publicizing the release of the new issue, creating the issue page, getting a table of contents up, and identifying the minimal updating goals for that issue. Once that is done, we will need people to search Wikitree for relevant profiles and update.
So, before I try setting up a project page and implementing some of the above, I'd like feedback. Am I wrong about some assumptions? Are there improvements or expansions to make with the setup?
Thanks for your help with this.