Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add preset for memorial=stolperstein #318

Closed
tordans opened this issue Dec 26, 2021 · 5 comments · Fixed by #964
Closed

Add preset for memorial=stolperstein #318

tordans opened this issue Dec 26, 2021 · 5 comments · Fixed by #964

Comments

@tordans
Copy link
Collaborator

tordans commented Dec 26, 2021

We have a lot of those special memorial stones in Germany and both the Wiki(data)/Data Item and OSM Community are recording them. It think a preset would be a nice recognition of this work.

However, the tagging seems be in a process of change, so we need to find a good preset tagging here.

Here is my research:

Preset

What tags to add to the preset:

  • historic=memorial – Required
  • memorial=stolperstein – Required, The presets reference
    • And not the IMO outdated memorial:type=stolperstein
  • name – Name of person
    • And not the IMO outdated memorial:name
  • inscription – Text on stone
    • And not the IMO outdated memorial:text
  • website – There are whole websites about his (example), which are useful to have so lets nudge users to add them
  • wikidata

More fields-Area:

  • image - Wikipedia image URL
  • memorial:addr – Wikipage was not sure which address, and I don't see it adding a lot of value, since this is geo referenced; therefore place in "more fields"
  • wikipedia- I would nudge for the wikidata ID instead, therefore place in "more fields"

What I would leave out:

  • memorial:ref=<123> – I don't understand where this official number should come from

Discuss

Questions we should talk about

  • See tagging above; @dieterdreist you wrote about this in 2018, what are your thoughts
  • How should iD handle the outdated tags? Should we add another, non-searchable preset for the old tags? Or even recommend a tag-update in iD?
@tordans tordans changed the title Add preset for memorial=Stolperstein Add preset for memorial=stolperstein Dec 26, 2021
@tyrasd
Copy link
Member

tyrasd commented Jan 18, 2022

Should only apply for Germany since this is where most of those stones are (right?)

Austria also has quite a few of them mapped: currently about 1.1k when including both tagging variants vs. 24k in Germany which is about the same order of magnitude when considering their relative population sizes. If I'm counting correctly, this leaves about 1.3k mapped objects remaining, most of which are probably scattered throughout Europe (I found about 230 in Italy and 100 in France, 70 in Spain).

According to wikipedia, these countries would in principle have Stolpersteine:
map of which countries have stolperstein memorials according to wikipedia


wikidata […] wikipedia

Wouldn't the subject:wikidata (and subject:wikipedia) tags be more appropriate?

@dieterdreist
Copy link
Contributor

from my understanding, subject:wikidata would be about the people who are commemorated on the stones, most of which are not famous and there is neither a wikidata nor a wikipedia article about them.

@tyrasd
Copy link
Member

tyrasd commented Jan 18, 2022

Since the raw wikidata tag should be about the individual Stolperstein memorials themselves, I assumed these would be even more unlikely to exist, but I was wrong: There are currently 16400 wikidata entries of individual Stolperstein memorials (14500 of which are geolocated – here's an example: https://www.wikidata.org/wiki/Q87722039). Not bad!

//edit: perhaps the wiki page needs to be updated about this. Currently, there is only a mention of the wikipedia tag and recommends subject:wikipedia:

wikipedia […] Falls ein spezieller Artikel vorhanden ist. Da es sehr unwahrscheinlich ist, dass ein Wikipediaartikel zu einem Stolperstein selbst existiert, sondern nur ein Artikel zur Person, wurde vorgeschlagen wikipedia:subject=* bzw. subject:wikipedia=* zu verwenden, […]

@tordans
Copy link
Collaborator Author

tordans commented Oct 10, 2022

@tyrasd what are your plans on those issues that rely on #351. Can we move them forward for the time being and refactor them once there is more login in to im prove the situation for translators? Or do you consider them blocked until that issues is resolved?

I would love to see this present going. But also the bike related issues that I started a while back.

@tordans
Copy link
Collaborator Author

tordans commented Oct 10, 2022

About the open discussion above:

wikidata vs. subject:wikidata

I the preset should stick with wikidata. Mappers are asked to add the wikidata entry of the corresponding stone, which is what the top level wikidata tag is for IMO.

How should iD handle the outdated tags? Should we add another, non-searchable preset for the old tags? Or even recommend a tag-update in iD?

To keep thinks simple, I would add unsearchable preset to at least show those old tags the same way. The question of how to harmonize the two schema can be raised later / elsewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants