Use of CategoryInfoBox in Cemetery categories

Question

Proposal: To use Template:CategoryInfoBox Cemetery on every cemetery category.

Template is mainly done. Suggestions to add something are welcome.

There are two base usages of the template. One to use on a Cemetery category and the other, to use on Cemetery grouping category.

For category pages:

{{CategoryInfoBox Cemetery
|name= Name of the cemetery. It represents just the title of the CategoryInfoBox Example: Pokopališče Žale
|image= Optional. Image name on WikiTree, that shows the cemetery.
|parent= Name of the lowest parent category that groups the cemeteries. Example: Slovenia Cemeteries
|project= Optional. Name of the project, that oversees the categories.
|location= Name of the lowest location category that the cemetery is located in. Example: Ljubljana, Slovenija
|wikitreepage= Name of the associated Free Space Page without the Space: prefix. Example: Belleview Cemetery
|wikidataID= Optional. WikiDataID of the cemetery. Only if the cemetery has Wikipedia/Wikidata page. Do not use the page of location. Example: Q338245
|findagraveID= Optional. ID of the cemetery on FindAGrave website. It is the number in URL of the cemetery. Example: 1983192
|billiongravesID= Optional. ID of the cemetery on BillionGraves website. It is the name and the number in URL of the cemetery, that is after /cemetery/ in the URL. Example: 188928
|webpage= Optional. Full URL of the cemetery webpage.
|coordinate= Optional. Longitude and latitude of the cemetery, separated by comma. It is displayed in URL on OpenStreetMap or Google. Example: 46.0712,14.5318
|startdate= Optional. Year of the first burial on the cemetery.
|enddate= Optional. Year of the last burial on the cemetery.
|TOC= yes Optional. Adds letter navigator for profiles
}}

For grouping pages:

{{CategoryInfoBox Cemetery
|name= Name of the group of cemeteries. It represents just the title of the CategoryInfoBox Example: Slovenia Cemeteries
|parent= Name of the lowest parent category that groups the groups of cemeteries. Example: European Cemeteries
|project= Optional. Name of the project, that oversees the categories.
|location= Name of the lowest location category that the cemetery group is located in. Example: Slovenia
|findagraveLocID= Optional. ID of area search on FindAGrave. Example: https://www.findagrave.com/cemetery/search?locationId=county_245
|profiles= no Optional. Displays Top Level template.
}}

To see usage examples, see Special:Whatlinkshere/Template:CategoryInfoBox Cemetery

Or search them on WT+ https://wikitree.sdms.si/function/WTCatContentSearch/Categories.htm?Query=CategoryInfoBox+Cemetery

If there are any questions, feel free to ask.

Comments

For the Web Page link, could it be titled, i.e. rather than "Web Page", have it be "Common Burying Ground at Sandy Bank"?

---

Just a small request, Aleš: I think it would be helpful for most of us to have additional examples for the Name, Parent, Project, and Location parameters, especially because different countries have different location structures.

If you don't want to include that much text within the template instructions, maybe a link to a free-space page containing examples for different countries would work.

---

Julie, there is a google spreadsheet, where you can see all parameters for all CIBs in use. There you can find all examples for certain region.

https://docs.google.com/spreadsheets/d/11XXJMy5-pN6rHJ2Tnx5pIi1cJ1LZR9ufJ90XJu9rZMg/edit#gid=76606774

It is updated daily.

---

Thanks, Aleš! Is that spreadsheet linked to the templates? I'm thinking that the everyday user is not going to want to or know how to go look at a spreadsheet to understand the parameters.

Is there a reason you don't want to include a few more examples on the template page??

---

That sheet is for Categorization project.

Each Template has quite detailed description of each parameter.

https://www.wikitree.com/wiki/Template:CategoryInfoBox_Cemetery

Now there is also added new way of defining parameters. That will be also used on new extension I am preparing. https://chrome.google.com/webstore/detail/wikitree%20/giodhdfeabddjnlhknbggojlgpnhanof It is almost finished for category pages. version 0.1.14 should be posted later today.

You have also What Links here on each template, where you can see alll examples.

---

Dana, That is probably already the name of the Category. I think Web Page clearly defines, that this is the link to a Web page associated with the cemetery.

---

Is “Category: “ supposed to be showing up in the (displayed) value of Location?

---

Yes. That way you know you will jump to a WikiTree Category page.

Answer 1

It looks very good..nice and clean looking.

There is utility in that adding the FINDAGRAVE ID number, which does not change. (Unlike the URL does, as we saw with the recent move to the new FINDAGRAVE.)

Easy to use, too.

Answer 2

I like it and I think it will ultimately solve some problems. Nice work.

Answer 3

I'm wondering if we could add a pipe in the Location field for the cemetery info boxes so it removes the Category:prefix like is done in the Migration templates?

Comments

Category prefix is intentionally displayed. I display it to distinguish between links to Space pages, Projects and Categories on WikiTree.

---

I can understand how distinguishing between links seems to be a valid point but, unless I'm mistaken, that field is configured only to link to a category in the first place by converting plain text to link.

What bothers me is the prefix interrupts how that field is read in the box and exposes wiki markup logic within the main content of a page.(note that all other boxes that use categories to link to locations use a pipe to remove the category prefix). A category is not a "location" in and of itself and page prefixes should not be stated inside a link within main page text as a general wiki style rule.

Even if the point was to eventually replace all Category links with Space page links (and thus the prefix was to help people know when they need to be replaced) it shouldn't matter either way what kind of link it is, so long as it goes to a page of a place the cemetery is located in where end users can get more information. They'll learn soon enough by clicking on it (or hovering) what kind of link it is.

---

You have some valid points, but the CategoryInfoBox has a goal to be used on all categories and there will be a lot of different combinations of page types.

Also from category lists there might be a problem to find Location category, since we have cemeteries with 5 and more parent categories. That is the reason that location category is repeated in the table.

Answer 4

Some changes add to a category; some are window dressing.  This one is window dressing, and now we are apparently all stuck with it.  Yippee!

Comments

J.,

Could you say more about how you see this as window dressing and not adding to a category ?

I'm not a huge fan of categories but this actually looks helpful.

---

I have to agree with Jillaine. The information contained in this template provides links to outside websites where additional information can be found. It also helps people understand the project they need to contact for more information and/or to volunteer to help.

It also consistently formats all cemetery pages, which is definitely needed.

Answer 5

has the problem with other languages been solved on this?  Last discussion on the subject, Cimetières got Cemetery added automatically to the parent category name.   

Comments

No. Until now only French and Sweden cemeteries seems to have localized hierarchy.

This could be solved automatically based on the cemetery text or with lang parameter which would be simpler. Another way would be to make separated copies of CIB templates for each language, but that might complicate the future development.

I guess you would want also texts in CIB translated. I could extend my translator to handle those texts.

Which CIBs do you want to have in french?

---

hmm, sounds like a whole lot of work for you, right now I am filling in the empty categories on cemeteries here with some data and sources, almost done that for existing cemeteries.  Not sure I want to carry on creating them after those are all fixed up.  Not really an interest of mine, just cleaning up the area for this province.

---

If you can live without localized CIBs for another year or two, I would postpone this. Maybe better solution will be possible in the future, as WikiTree develops.

---

sounds good to me, don't know about others who have various languages set up in tree structure.

---

The great majority of French language cemetery categories are for Québec cemeteries, so what is good for Danielle is good for me too.

Most of the cemetery categories in France are for military cemeteries (either American or Commonwealth), they are set up primarily in English and the English CIB works fine. There is a handful of Parisian cemeteries too, but we can definitely live without a CIB for these.

Answer 6

I really like it and I find it adds much usable information to the categories in a standard format that will be of great help to me even when I encounter a language I don't understand.  

I especially like that the information in Category Info Boxes makes it possible to automate reports which help us keep the category structure maintained and to find things that need correcting.