npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

gensearch

v2.4.3

Published

Generate search links for genealogy websites

Downloads

11

Readme

npm Build Status Coverage Status

gensearch

Generate search links for a many genealogy websites.

Try the Demo

Usage

// Generate a search link for FamilySearch
var url = gensearch('familysearch', {
  givenName: "Joe William",
  familyName: "Clark"
});

// Some options can be changed. Here we modify the birth year range
var url = gensearch('familysearch', data, {
  birthRange: 5
});

// Or we can set the configuration option once and have it apply to all future searches.
gensearch.config('familysearch', {
  birthRange: 5
});

// We can also set options for multiple sites at once
gensearch.config({
  familysearch: {
    birthRange: 5
  },
  archives: {
    deathRange: 10
  }
});

Install

Web

Via the CDN unpkg:

<script src="//unpkg.com/gensearch@latest/dist/gensearch.min.js"></script>

Node

npm install gensearch
var genSearch = require('gensearch');

Schema

  • givenName
  • familyName
  • birthPlace
  • birthDate
  • deathPlace
  • deathDate
  • marriagePlace
  • marriageDate
  • fatherGivenName
  • fatherFamilyName
  • motherGivenName
  • motherFamilyName
  • spouseGivenName
  • spouseFamilyName

Sites

americanancestors

http://www.americanancestors.org/

var url = gensearch('americanancestors', data);

ancestry

http://ancestry.com

var url = gensearch('ancestry', data, [options]);

| option | default | notes | |--------|---------|-------| | db | | Search within a specific database. This value equates to the 'db' parameter value used by Ancestry. |

archives

http://archives.com

var url = gensearch('archives', data);

| option | default | |--------|---------| | birthRange | 2 | | deathRange | 2 |

billiongraves

http://billiongraves.com/

var url = gensearch('billiongraves', data, [options]);

| option | default | |--------|---------| | yearRange | 2 |

chroniclingamerica

http://chroniclingamerica.loc.gov/

var url = gensearch('chroniclingamerica', data);

familysearch

https://familysearch.org

var url = gensearch('familysearch', data, [options]);

| option | default | notes | |--------|---------|-------| | birthRange | 2 | | deathRange | 2 | | marriageRange | 2 | | collectionId | | Only search within a specific collection. |

findagrave

http://findagrave.com

var url = gensearch('findagrave', data);

findmypast.co.uk

http://findmypast.co.uk

var url = gensearch('findmypast.co.uk', data, [options]);

| option | default | notes | |--------|---------|-------| | event | | Type of event to search for. Valid values are birth, death, and other. The otherDate and otherPlace options are used when event is other. | birthRange | 2 | | deathRange | 2 | | otherRange | 2 | | otherDate | | Only used when event is other. | | otherPlace | | Only used when event is other. |

findmypast.com

http://findmypast.com

var url = gensearch('findmypast.com', data, [options]);

| option | default | notes | |--------|---------|-------| | event | | Type of event to search for. Valid values are birth, death, and other. The otherDate and otherPlace options are used when event is other. | birthRange | 2 | | deathRange | 2 | | otherRange | 2 | | otherDate | | Only used when event is other. | | otherPlace | | Only used when event is other. |

fold3

http://fold3.com

var url = gensearch('fold3', data);

Only givenName and familyName are used for Fold3 searches.

genealogieonline

http://genealogieonline.nl/en/

var url = gensearch('genealogieonline', data, [options]);

| option | default | |--------|---------| | birthRange | 5 | | deathRange | 5 |

genealogybank

http://genealogybank.com

var url = gensearch('genealogybank', data, [options]);

| option | default | notes | |--------|---------|-------| | lifespan | 90 | If either a birthDate or deathDate exists, but not both, then this value is used to approximate the missing year. For example, if the birthDate is 2 Feb 1766 and no deathDate is given then we would add lifespan to the birth year to get an approximate death year of 1856. | | datePadding | 5 | This value is substracted from the calculated birth year and added to the calculated death year. |

geneanet.en

http://en.geneanet.org/

var url = gensearch('geneanet.en', data, [options]);

| option | default | notes | |--------|---------|-------| | place | birth | Determines whether the birth or death place is used for searching. Values: birth or death. |

gengophers

https://www.gengophers.com

var url = gensearch('gengophers', data);

geni

http://geni.com

var url = gensearch('geni', data);

Only givenName and familyName are used for Geni searches.

google

https://www.google.com

var url = gensearch('google', data);

mocavo

http://www.mocavo.com/

var url = gensearch('mocavo', data);

myheritage

http://www.myheritage.com

var url = gensearch('myheritage', data);

newspapers

http://www.newspapers.com/

var url = gensearch('newspapers', data, [options]);

| option | default | notes | |--------|---------|-------| | lifespan | 90 | If either a birthDate or deathDate exists, but not both, then this value is used to approximate the missing year. For example, if the birthDate is 2 Feb 1766 and no deathDate is given then we would add lifespan to the birth year to get an approximate death year of 1856. | | datePadding | 5 | This value is substracted from the calculated birth year and added to the calculated death year. |

nla trove

http://trove.nla.gov.au/

var url = gensearch('nlatrove', data);

openarchives

http://openarch.nl

var url = gensearch('openarchives', data);

Only givenName and familyName are used for Open Archive searches.

usgenweb

http://www.usgwarchives.net/

var url = gensearch('usgenweb', data);

werelate

http://werelate.org

var url = gensearch('werelate', data, [options]);

| option | default | |--------|---------| | birthRange | 2 | | deathRange | 2 |

wikitree

http://www.wikitree.com/

var url = gensearch('wikitree', data);

worldvitalrecords

http://worldvitalrecords.com

var url = gensearch('worldvitalrecords', data, [options]);

| option | default | |--------|---------| | dateRange | 2 |

Contribute

Setup

git clone https://github.com/rootsdev/gen-search.git
cd gen-search
npm install

Add a site

  1. Create the site file in the src/sites directory. Look at archives.js for a simple example or familysearch.js for a more complex example.
  2. Add the new site to the src/search.js site list, in alphabetical order please.
  3. Add a test file in the test/sites directory. Look at any of the other site test files for an example.
  4. Run tests with npm test. The gensearch.js file will be automatically built with browserify before the tests are run.
  5. Document the new site in the README file, in alphabetical order please. Be sure to add a link in the site list just before the site specific docs.
  6. Commit and submit a pull request.