Wikidata:Property proposal/EK number
EK number edit
Originally proposed at Wikidata:Property proposal/Creative work
Description | Identifier for an artwork in the Entartete Kunst database of the Freie Universität Berlin |
---|---|
Represents | degenerate art (Q156460) |
Data type | External identifier |
Domain | work of art (Q838948) |
Allowed values | (string consisting of numbers) |
Example | Die Auswanderer (Q30070932) → 16022 |
Source | http://emuseum.campus.fu-berlin.de/eMuseumPlus?service=ExternalInterface&lang=en |
Planned use | Mix'n'match? (the 'bookmarkable links' do not contain the EK number, however...) |
- Motivation
Historically quite significant, right? Because the database uses eMuseum software, however, scraping it might be hard. See some explanation about the EK numbers - they are not really identifiers, but actual numbers assigned to the artworks during times of confiscation. Spinster 💬 20:27, 25 November 2017 (UTC)
- Discussion
- Support It would be nice to add all the catalogs listed on that site too, if the 1937 travelling exhibition published them. Jane023 (talk) 13:05, 26 November 2017 (UTC)
- I agree we should definitely do something with the "Entartete Kunst", but I'm not convinced a separate (string) property is the way to go. Wouldn't this be a more straightforward solution? Multichill (talk) 16:19, 26 November 2017 (UTC)
- I don't think this should be approached like a catalog. The Entartete Kunst database is just one possible means to bring these artworks together. It's all about the numbers themselves, which were given to the artworks by the nazis, are often still physically present on the works, and I assume are also often mentioned in literature. More than being part of a neutral-ish catalog, these numbers are an intrinsically political part of an artwork's life and history. Having them as a separate property would make researching, querying and listing them easier than when we let this become buried in all the catalogs we already have, IMO. Spinster 💬 21:08, 26 November 2017 (UTC)
- I would prefer using external-id here. ChristianKl (✉) 10:00, 27 November 2017 (UTC)
- Support however I agree with ChristianKl this seems like an external-id - the problem is the EK ID is not used in the example link, so we don't seem to have a good formatter URL. I took a look at their search form (you can search by EK ID) but it wasn't obvious how to generate a URL that would do the job. ArthurPSmith (talk) 16:05, 27 November 2017 (UTC)
- Comment That's also a reason why I wouldn't do an external ID. When their website architecture changes for the better, I assume we can always convert the values to identifiers? Spinster 💬 20:06, 28 November 2017 (UTC)
- @Spinster: I think it's better to set the datatype to external-id now even without the formatter URL, hopefully we will have one later. Changing datatypes requires some developer attention which may be hard to get. ArthurPSmith (talk) 18:29, 29 November 2017 (UTC)
- Comment That's also a reason why I wouldn't do an external ID. When their website architecture changes for the better, I assume we can always convert the values to identifiers? Spinster 💬 20:06, 28 November 2017 (UTC)
- Support David (talk) 08:20, 28 November 2017 (UTC)
- Support. YULdigitalpreservation (talk) 18:24, 29 November 2017 (UTC)
- @Spinster, Jane023, Multichill, ChristianKl, ديفيد عادل وهبة خليل 2, YULdigitalpreservation: Done ArthurPSmith (talk) 20:50, 8 December 2017 (UTC)