This page is a part of the Rivet Name Study project. The purpose of this page is to serve as a central place to store information about where actual documents and records can be or have been found relevant to the Rivet Name Study project. The intent is for the project to review and document on WikiTree every known Rivet, Rivett, and Rivette (hereinafter written as Rivet*) record.
The entries on this page should be organized by location. It can include either physical or virtual repositories. This page is not intended to include online family trees or records derived from user-supplied pedigrees and family trees, including FamilySearch's IGI, Ancestry's Edmund West collections, personal online trees, etc. This should be limited to only those collections derived from original or well documented secondary sources.
Note that this process assumes that a project member has committed to review an entire collection, or location within a collection, for relevant names to this name study. If that is not the case, then entries for that collection should specify exactly what was searched and reviewed.
How to use this page:
- Select a collection or repository of your choice that isn't already mentioned here. Review it thoroughly for relevant Rivet* records. The review can be done by using search terms, using an index if available, or by manually browsing each record.
- If a project member reviews a collection and finds NO Rivet* records, it should be entered on this page and noted as "no records found," how it was reviewed, and then signed by the user with the four tildes (i.e., ~~~~). That might keep people from going to it in the future in the hopes of finding something that we already know is not there!
- If records are found for a particular collection, it should be noted whether or not the records have all been added to relevant WikiTree profiles, with an explanation of what was or was not entered and what still needs to be done. As above, the note should also include how it was reviewed, and then signed by the user with ~~~~.
- When a project member adds a repository, it should be entered under the applicable location heading using an asterisk (*) to begin the line. If there isn't an appropriate location heading, one should be created. In the case of records within the United States of America, the structure should be by Country, State, County/Parish, City if applicable, and then Repository. Other countries should be organized by their respective standard jurisdictions.
- If records are known to be available in both a physical and a virtual repository, entries should ideally include the physical location as well as the URL, but noting which was actually viewed. Please include links to online collections even if it is behind a paywall, if you can. If a collection is available in either free or subscription sites, enter both if known. We do not discriminate against subscription sites, as they can be valuable resources.
And yes, I considered putting this into a table format, but the wiki coding can be difficult and confusing, so I chose to do it in this simpler format for now.
As this page grows, it may be necessary to split it into multiple pages by location or jurisdiction. We'll cross that bridge when we get to it!