FreeUKGen / MyopicVicar

MyopicVicar (short-sighted clergyman!) is an open-source genealogy record database and search engine. It powers the FreeREG database of parish registers, the FreeCEN database of census records, the next version of FreeBMD database of Civil Registration indexes and other Genealogical applications.
45 stars 15 forks source link

URL based enhancements #1871

Open PatReynolds opened 5 years ago

PatReynolds commented 5 years ago

A suite of URL based enhancements. Includes: 1/ permanent urls i.e. https://www.freereg.org.uk/search_records/58185baee93790ec75142e42 always takes you to the same record. Needed because it underpins the following enhancements. Part of #1144

2/ Citations - permanent url and data about the record and its publisher (us!) in a range of formats (formats prescribed by organisations such as the MLA, Evidence Explained and Wikitree, which we might seek to influence, but are independent, and we must follow their rules, even if they seem inappropriate to some genealogists. That's one of the reasons we offer a range. #1374, which needs #1098

3/ prettified urls for researchers (citation-like urls that are not citations) the permanent url expressed as the permanent url plus text about person, event, place and date. They help a researcher identify which of six records they noted down as being interesting were the two that might be Great-Uncle-Harry, and the four that might be Great-Aunt-Harriet. They might be used to share with others, who will use them in a similar way. For full documentation (e.g. on a family tree) a citation is needed. creation is part of #1144 Grabbing is part of #1870

4/ pages with prettified urls for SEO i.e. Search engine crawling and landing pages for open records with associated prettified url - may contain less/different data to the prettified url for researcher #1134

5/ buttons (or other solution) to enable users to grab permanent URLS and to share on social media #1870

6/ linked open data #1875 - an epic which needs populating. Work above (apart from permanent url) does not impinge on this, and so can be developed without waiting for #1875 to be populated

needs #1143 needs #1144 Needs #1870 Needs #1098 - issue, not feature Needs #1374 Needs #1875 (epic)

Captainkirkdawson commented 5 years ago

Point 1 above. The permanent url. Rather than use the code originally developed to make the search_id parameter optional we proceed straight away with #1854 which proposes to use internal storage to achieve the same goal. Have moved that into in progress and will collaborate with @benwbrum on its development and implementation

Captainkirkdawson commented 5 years ago

Point 2 above. Citation is available and running for both reg (test3 reg) and cen (test2 cen)