Property talk:P1260

Documentation

• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

Swedish Open Cultural Heritage URI
identifier

Description	Swedish National Heritage Board (Q631844) has set up a webservice for the cultural monuments, protected buildings and items that are connected to a number of museums in Sweden.
Associated item	Swedish National Heritage Board (Q631844)
Applicable "stated in" value	Swedish Open Cultural Heritage (Q7654799)
Data type	External identifier
Template parameter	ex: sv:Mall:RAÄ-nummer and commons:Template:Fornminne
Domain	cultural heritages in Sweden (note: this should be moved to the property statements)
Allowed values	[a-zA-Z].+\d.*
Example	Hidinge church (Q2892790) → raa/bbr/21300000003265 (RDF) Uppland Runic Inscription 932 (Q7899135) → raa/fmi/10028200010001 (RDF) Maria Magdalena kyrka, Lund (Q10577192) → raa/bbra/21320000019150 (RDF) Maria Magdalena kyrka, Lund (Q10577192) → raa/bbrb/21420000014623 (RDF) no label (Q19931129) → shm/art/940920F11 (RDF) Möjbro Runestone (Q1360628) → shm/inventory/24203 (RDF) Kylver Stone (Q1795104) → shm/object/267753 (RDF) no label (Q19758488) → GSM/objekt/20269 (RDF) Carl Hårleman (Q1038985) → LSH/agents/14474 (RDF) no label (Q19931017) → nomu/object/NM0042820 (RDF) Ernst Almquist (Q5547606) → SMVK-EM/name/1174346 (RDF)
Commons example	→ raa/kmb/16000700021628 → raa/kmb/16000200151051 → raa/kmb/16001000040784
Formatter URL	https://kulturarvsdata.se/$1
Related to country	Sweden (Q34) (See 117 others)
See also	Museum of Gothenburg object ID (P10805)
Lists	Search Commons for files with property Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other external identifier Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Complex constraint violations/P1260 Database reports/Constraint violations/P1260 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 173,179 Main statement 173,046 >99.9% of uses Qualifier 17 <0.1% of uses Reference 116 <0.1% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Format “[a-zA-Z].+\d.*”: value must be formatted using this pattern (PCRE syntax). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1260#Format, SPARQL

Allowed entity types are Wikibase item (Q29934200), Wikibase MediaInfo (Q59712033): the property may only be used on a certain entity type (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1260#Entity types

Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1260#Scope, SPARQL

This property is being used by: sv:Mall:BBR-länk sv:Mall:RAÄ-nummer sv:Mall:LSH-länk sv:Mall:Arme-länk sv:Mall:NOMU-länk sv:Mall:UPMU-länk sv:Mall:Kulturen-länk sv:Mall:TEKM-länk sv:Mall:Vasa-länk sv:Mall:VGM-länk sv:Mall:SMVK-VKM-länk sv:Mall:SMHA-länk sv:Mall:Fornvännen-länk sv:Mall:DFH-länk sv:Mall:BHM-länk sv:Mall:GNM-länk sv:Mall:SMVK-MM-länk sv:Mall:KLVM-länk sv:Mall:SMVK-OM-länk sv:Mall:SMVK-EM-länk sv:Mall:SHM-länk sv:Mall:KMB-länk sv:Mall:Flygvapenmuseum-länk sv:Mall:Evighetsrunor Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Format constraint for detecting syntax errors; allows both machine-readable and human-readable URLs (with suffix '/html'). Format constraint for machine-readable URLs is preferred, see this discussion, further down. Format constraint to explicitly track items using the human-readable URL key:

Missing qualifier for "raa/fmi/" values
Values starting with "raa/fmi/" should always have RAÄ number (P1262) as a qualifier. (Help)
Violations query: SELECT ?item WHERE { ?item p:P1260 ?statement . ?statement ps:P1260 ?val . FILTER (STRSTARTS(?val, 'raa/fmi/')) . FILTER NOT EXISTS { ?statement pq:P1262 ?x } }
List of this constraint violations: Database reports/Complex constraint violations/P1260#Missing qualifier for "raa/fmi/" values

Institutions using Kulturarvsdata

This is list of institutions using Kulturarvsdata with their identifiers and an incomplete list of identifiers used for sub-collections.

• AERO - Aeroseum (Q10401895)
  • object
• arkm - Swedish Centre for Architecture and Design (Q4356728)
  • object
  • photo
• DRMWEB - Dramawebben
  • nodeq
• GSM - Museum of Gothenburg (Q3107846)
  • objekt
• Kulturen - Kulturen (Q1363442)
  • objekt
• LSH - Livrustkammaren och Skoklosters slott med Stiftelsen Hallwylska museet (Q10568223)
  • objects
• raa - Swedish National Heritage Board (Q631844)
  • bbr - Bebyggelseregistret
  • bbra - Bebyggelseregistret
  • bbrb - Bebyggelseregistret
  • bbrp - Bebyggelseregistret
  • fmi - Fornsök
  • fornvannen - Fornvännen (Q4162197)
  • kmb - Kulturmiljöbild
  • samla
• shm - Swedish History Museum (Q1726607)
  • inventory - Inventory-ID
  • object - Object-ID
• TUM - The Unstraight Museum
  • object

More, in alphabetical order:

• ablm
• ajtte
• arme
• bhm
• dfh
• enk
• fmb
• gfm
• gnm
• hem
• heo
• jfl
• jm
• kbg
• klvm
• lsh
• mili
• mm
• nomu
• pm
• rsms
• shfa
• sk
• sm
• smha
• smm-mm
• smm-sm
• smm-vm
• smvk-em
• smvk-mm
• smvk-om
• smvk-vkm
• socken
• tekm
• tes
• upmu
• vax
• vbg
• vm
• wws

Many of these are mapped at commons:Category:External link templates using Kulturarvsdata and w:sv:Kategori:Externa länkmallar via K-samsök. /André Costa (WMSE) (talk) 07:40, 4 May 2015 (UTC)

@André Costa (WMSE): Could we for raa also add bbrp? That would make it possible to match the architects that Swedish National Heritage Board (Q631844) covers. Example (json-ld). Ainali (talk) 09:35, 20 December 2016 (UTC)

OK by me. /Lokal Profil (talk) 15:16, 20 December 2016 (UTC)

Ok, I'll try to add it. Ainali (talk) 14:09, 4 January 2017 (UTC)

Add catalog / type of mapping

I suggest that an aggregator like this should in Wikidata use a qualifier state the original source, using pattern matching is not a good design pattern...

• I added catalog (P972)
• as we get more mature in mapping domains its also best practise to specify mapping relation type (P4390)

– Salgo60 (talk) 07:46, 20 June 2019 (UTC)

Here is a list of catalogs in SOCH. These are however "services" and they are not stable nor do the always represent the catalog of origin. I removed the ones you made up and added to a bunch of items please do not add false information to Wikidata in the future. Abbe98 (talk) 07:02, 28 June 2019 (UTC)

/html/ ending

There are two main ways of giving these identifiers.

• 'institution/database/html/<ID>', e.g. 'raa/bbr/html/21310000000827' or
• 'institution/database/<ID>' e.g. 'raa/bbr/21310000000827'

The first is a redirect to the human readable webbpage ([1] for the first example). The second gets you to the official entity in the database (rdf). I would definitely recommend using the latter for wikidata where the linked data interface makes more sense. If so the description (in Swedish) should probably also be changed and we should go through existing identifiers and change these. /André Costa (WMSE) (talk) 07:55, 4 May 2015 (UTC)

I had a similair discussion about Riksdagen person-ID (P1214) some days ago. This one is more difficult to change, since the difference is in the middle of the code. -- Innocent bystander (talk) 15:13, 4 May 2015 (UTC)

I changed the description to remove the /html/ ending. Do we know if there are any plans to add support for additional $ parameters in URL-like strings? Some properties, like P1413 (P1413), will not work without it. Väsk (talk) 16:16, 4 May 2015 (UTC)

Could we format a Template:Constraint:Format to discover statements that include /html/? I don't know how to make a RegExp for this, but something like 3-7 letters, forward slash, 3-10 letters, forward slash, 1-14 numerals should discover both unnecessary htmls and numbers without prefixes. Väsk (talk) 16:41, 4 May 2015 (UTC)

A second thought: It's easier for a bot or a template to remove a few letters like "/html" than adding them in the correct position. In C# I just have to add a line like t = t.Replace("/html", ""). Adding "/html" to get a human-readable version is more tricky! -- Innocent bystander (talk) 08:51, 5 May 2015 (UTC)

@Innocent bystander: While it is indeed easier to make human readable links using the /html/ style it should be noted that this is in fact not part of the actual id.included in the actual id. So the choice would be weather to use something which is easier for allowing Wikipedia to make links or something which is correct (and therefore more usable everywhere else)

@Väsk: I'm not sure the regex is that simple. If I remember correctly from the templates (linked above) there is no guarantee that the id is purely numeric or that there aren't more subparts of the prefix. /André Costa (WMSE) (talk) 14:49, 5 May 2015 (UTC)

I did not talk about how easy it is to write the id here at Wikidata. I guess that mainly will be done by bot anyway. I talked about how easy it would be to design templates to change from machine-readable to man-readable compared with the other direction.

I think it could be worth to try to add such a sulution. The regex for Scandinavian Runic-text Database ID (P1261) looks awful, but it looks like it works.

I guess there are jokers who allow both digits and a-z-letters. That there is a violation of a constraints, does not make it automaticly wrong. -- Innocent bystander (talk) 06:19, 6 May 2015 (UTC)

Sorry. I didn't mean easier for Wikidata but (like you) easier for (human-readable) links, through templates. But the cost of making that easier would be that we have identifiers that are not actually correct (since /html/ is not part of the id. /André Costa (WMSE) (talk) 14:25, 11 May 2015 (UTC)

A temporary solution could be to use Kringla.nu in the URL formatter instead ([2][3]). A link to the original database would be preferable, as the data in Kulturarvsdata is incomplete and some of the context gets lost, but Kringla.nu does present the data in human-readable form with some additional features and a (tiny) link to the originating database. Väsk (talk) 15:27, 11 May 2015 (UTC)

Commented-out version of the format constraint comprising "/html" suffix to produce human-readable URLs

Constraint:Format|pattern=(raa/(bbr(|a|b)|fmi)/html/\d{14}|shm/art/html/9\d{5}F(1\d|[1-9])|shm/inventory/html/[1-9]\d{0,4}|shm/object/html/[1-9]\d{0,6}|GSM/objekt/html/[1-9]\d{0,4}|LSH/agents/html/[1-9]\d{0,4}|nomu/object/html/NM\d{7})

-- LaddΩ chat ;) 14:07, 19 January 2016 (UTC)

@Tore_Danielsson, Väsk, André Costa (WMSE), Innocent bystander, Ainali: any news/update/change in status/thoughts on using kulurarvsdata and formatter URL that is human readable?

I feel kulturarvsdata is the "only" property in Wikidata that not goes to a human readable page which feels odd

Feels like a mess that if you should check the data in Wikidata then you need to understand how to change the URL to a human readable form?

Another example that I found that feels not user friendly and wrong because lack of human readable form is to have this URL in reference URL (P854) Example....

• Bååtska palatset (Q10438659)
• heritage designation (P1435)
• Q10438659#P1435 ==> you have data enskild byggnadsminnesanläggning and as qualifier
  • stated in (P248) Bebyggelseregistret with a
  • reference URL (P854) referens-url a non human readable URL http://kulturarvsdata.se/raa/bbr/21300000010178
• My suggested solution
  • a formatter URL that makes it human readable always if possible
  • use properties ==> in the last example better to use Swedish Open Cultural Heritage URI (P1260) and have a human readable property

If linked data and museums and registers should be connected and used we need to make it easy to use/access step 1 is make it human readable..... - Salgo60 (talk) 12:00, 12 November 2017 (UTC)

@Salgo60: There is now more than one property for this and, to be honest, I have no ------- clues what these other properties are designed for. -- Innocent bystander (talk) 07:30, 13 November 2017 (UTC)

common.js

importScript('User:Salgo60/kulturarvsdata.js'); // see script from Abbe98 https://github.com/Abbe98/human-readable-kulturarvsdata

@Yger: add the above line in your common.js It is a small script by Abbe98 that change the URL for Swedish Open Cultural Heritage URI (P1260) to the human readable version compare my User:Salgo60/common.js - Salgo60 (talk) 20:00, 11 November 2018 (UTC)

Dublicate URIs in examples?

I see that some of the examples have duplicated claims, where both the raw URI and the HTML one is used. Is that relay a good solution? Shouldn't Wikidata always prefer the raw RDF one? When does it make sense to have both the raw URI and the HTML one? --Abbe98 (talk) 10:47, 13 September 2016 (UTC)

@Abbe98, Innocent bystander: This come back to the section on /html/ ending above. That said I would still say both duplicates and the html version should be avoided. Programmatically it should be fairly easy to do a right handed partition on "/" and inject the "/html/" string (something like the following in python parts = value.rpartition('/'); html_version = parts[1] + '/html/' + parts[2]). That solves the problem of handling these id's in Wikipedia infoboxes etc., what we loose is the ability to click on the id in the Wikidata UI and end up in the html page since the UI doesn't allow that type of string manipulation and kulturarvsdata doesn't apply content negotiation to the "main" url @Ainali.

Since there currently doesn't seem to be any values containing html though now would be a good time to disallow the html version if that is what we want to do. /André Costa (WMSE) (talk) 10:28, 27 January 2017 (UTC)

I got a user-script for the Wikidata UI issue and the fact that there is no instances of URIs pointing to the HTML version is my fault too... pip install ksamsok is a thing too(whenever you need to deal with SOCH URIs). So I definitively thinks that html(jsonld/xml etc.) should be disallowed. --Abbe98 (talk) 15:58, 27 January 2017 (UTC)

FYI: An RAÄ internal CR has been created for supporting en:content negotiation by Abbe98 is my understanding - Salgo60 (talk) 07:14, 18 January 2019 (UTC)

en:content negotiation is now available since 8 dec link - Salgo60 (talk) 22:27, 8 December 2020 (UTC)

mixing subjects

@André Costa (WMSE), Ainali, Abbe98: et al! It looks like you intend to start a project where you will massimport data from fmis? That is fair with me, I love to work with that! But you have to consider one thing! The article sv:Björkå is about a "småort" and two "gravfält". Multiple-subject WP-articles is one thing, but multiple-subject items is a "ursäkta franskan: en finne i arslet". Is it the "småort" or "Holms gravfält" who has a population of 67 persons. Is it the småort or gravfält who "has part:burial mound quantity:27". Is it the graves or the settlement who has "shape:oval with a pit at the top". -- Innocent bystander (talk) 14:20, 29 January 2017 (UTC)

After reading Help:Handling sitelinks overlapping multiple items I think that Wikidata item should be rebuilt to have has part(s) (P527) with three new items, one for the "småort" and one for each "gravfält". The same could be done for all other "bundled" articles on svwiki. Some check for items with instance of (P31)minor locality in Sweden (Q14839548) and also Swedish Open Cultural Heritage URI (P1260) should be done before any import to help reveal such items. Ainali (talk) 20:11, 29 January 2017 (UTC)

@Innocent bystander, Alicia Fagerving (WMSE), Ainali, Abbe98: The plan is to import the data in the WLM database to Wikidata. FMIS is probably not the first one, but likely one of the first. I agree with Ainali that these should definitely be three separate items with the item connecting to the Wikipedia article containing a has part(s) (P527) (only?). For importing the WLM data I think the main issue will be to detect any false positives. E.g Björkå (Q2368410) contains Swedish minor urban area code (P776) so it cannot be a FMIS object (even if it contains a RAÄ number (P1262)). Another warning signal could be that w:sv:Lista över fornlämningar i Sollefteå kommun#Överlännäs links to w:sv:Björkå via the redirect w:sv:Björkå gravfält. I think a good first start would be to ensure RAÄ number (P1262) has some sensible constraints for instance of (P31). /André Costa (WMSE) (talk) 10:11, 30 January 2017 (UTC)

@Innocent bystander, André Costa (WMSE), Ainali, Abbe98: Examples like this make me more and more in favor of just mass-removing all claims that use RAÄ number (P1262) right before starting the import. That way, new items for "Holms gravfält" and "Björkå gravfält" will be created from scratch, without overlapping with Björkå (Q2368410). Not sure about the has part(s) (P527) -- in this case, it's about an object located in a village/town, and I haven't really seen this property used like that. And if an item in the Wikipedia list links to a redirect or to an article section (indicating that an article about this particular thing does not exist), the link could be ignored. --Alicia Fagerving (WMSE) (talk) 11:13, 30 January 2017 (UTC)

sv:Hemsjö, Alingsås kommun is an example of an article on svwiki with multiple subjects, and with a template with WD-support to extract data from three different items. (1. The item about the pair, 2. The item abut the "tätort", 3. The item about the "småort".)

No template is today adapted to the situation in sv:Björkå. One problem here is that this template-solution (based on the Geobox) is very expensive in terms of how much resources the templates and modules needs to render the page. -- Innocent bystander (talk) 11:52, 30 January 2017 (UTC)

@Alicia Fagerving (WMSE): Of the around 1100 items with RAÄ number (P1262) only around 100-200 seem to be wrong. I can clean that up manually this week so no need for mass removal. Ainali (talk) 12:38, 30 January 2017 (UTC)

@Ainali: True, I was thinking in the context of Property_talk:P1262#Qualifier_to_Cultural_heritage_database_in_Sweden_.28P1260.29.3F -- that is, removing the RAÄ number as a standalone statement and moving it to qualifier. --Alicia Fagerving (WMSE) (talk) 12:54, 30 January 2017 (UTC)

@Alicia Fagerving (WMSE): Ah, I had missed the recent development in that discussion, but it makes perfect sense. And then your proposal about botfixing standalone statements is something I support. Ainali (talk) 09:12, 31 January 2017 (UTC)

@Alicia Fagerving (WMSE), Ainali, Innocent bystander: For the Wikidata items corresponding to Wikipedia articles on multiple subjects the needed action would be threefold: Break out the FMIS item into a separate item, break out the småort info into a separate item, replace the contents of the Wikipedia-article-item with two has part(s) (P527) claims and some suitable instance of (P31) (something more specific than class (Q17519152) ideally). A fixing of these 100-200 objects would be needed whether or not we then change to P1260 as a qualifier only.

I'm not sure the Infobox issue is a blocker here. sv:Björkå already uses three infoboxes to deal with the fact that it is actually supposed to be multiple articles. We shouldn't expect templates, or the associated Lua to be the solution for that. A potential work-around for this case would be if the templates could accept a parameter which was "show me as if I was <this> wikidata id". /André Costa (WMSE) (talk) 10:14, 6 February 2017 (UTC)

RE: "show me as if I was <this> wikidata id" is fully possible to implement! I do not have the time to change the Ortsfakta WD-template now, but it is rather straightforward to fix. -- Innocent bystander (talk) 09:04, 7 February 2017 (UTC)

I made a stab at Björkå. Björkå (Q2368410) is now split up and has part(s) (P527): Björkå gravfält (Q28731191), Holms gravfält (Q28731194) and Björkå (Q28731198). Is that a way to go? Ainali (talk) 09:27, 8 February 2017 (UTC)

In my book the above separation of Björkå (Q2368410) looks to be right. =) /André Costa (WMSE) (talk) 14:18, 8 February 2017 (UTC)

"Good patterns"

I think it would be good when we map Swedish Open Cultural Heritage URI (P1260) to RAÄ that we also use mapping relation type (P4390) together with

• close match (Q39893184)
• exact match (Q39893449)
• related match (Q39894604)
• broad match (Q39894595)
• narrow match (Q39893967)

so the WD reader understands if we use the same concept that RAÄ use or if its nearly the same - Salgo60 (talk) 15:33, 27 August 2018 (UTC)

Suggested changes to property

The Kulturarvsdata property has primarily been used for buildings and heritage sites, however outside of Wikidata-land its used for a lot of different types of records, mainly ones representing an item found in archives. This is currently not reflected in the constraints of this property.

Suggested changes to constrains:

• Removal of item requires statement constraint heritage designation
• Removal of item requires statement constraint country Sweden
• Removal of item requires statement constraint coordinate location
• Removal of item requires statement constraint located in the administrative territorial entity
• Removal of distinct values constraint

The second subject is the format of the id, the examples and Regex suggest that this property supports values like <inst>/<serv>/<id> as well as <inst>/<serv>/html/<id>. Although the later is supported and many simliar formats as well, there is not a unified commitment at the SNHB to provide longterm support for these URLs. URLs of this type has been changed to the URI by bots for at least two years. The format Regex also defined the allowed service and institution values, however most of the used values are missing from the Regex and there are over 60 values for institutions and over 120 for services.

Suggested changes to format Regex:

• Simplified format Regex .+\/.+\/.+
• Removal of all HTML URL examples.

Abbe98 (talk) 13:28, 10 December 2018 (UTC)

Notifying @Lokal Profil, Alicia Fagerving (WMSE): who have been heavy users of this property.

Bebyggelseregistret

Should buildings in Bebyggelseregistret use this property or should I propose a new property for that database? They are not visible in Kringla. Is Bebyggelseregistret part of K-samsöm/SOCH?

Example: https://www.wikidata.org/wiki/Q96035332 / http://kulturarvsdata.se/raa/bbr/html/21420000009479 / http://www.kringla.nu/kringla/ingatraffar?text=kvarteret+havssvalget

Ambrosiani (talk) 11:43, 4 June 2020 (UTC)

@Ambrosiani: Everything in BBR is available in SOCH/Kringla as proven by the kulturarvsdata.se link above. The building in question can be found here on Kringla.nu. I have added third-party formatter URL (P3303) to this property to make the relation to Kringla.nu clearer. Abbe98 (talk) 20:49, 4 June 2020 (UTC)

@Abbe98: 🤦‍♂️ oops. Shouldn’t have used ”kvarteret” in my search. Ambrosiani (talk) 13:18, 5 June 2020 (UTC)

Link rot

FYI we did a test 2020 jun 30 of abt. 160 000 links to kulturnav used in Swedish Wikipedia and about 4% had problems --> Ok: 156539 Not ok 7604

• checkkulturarv Wikipedia links.py

No action and no official error reporting has been done and no official feedback from RAÄ - Salgo60 (talk) 10:45, 20 September 2020 (UTC)

Update to link resolution

From 2020-12-08 kulturarv.se links will take en:content negotiation into account. I.e. if you follow the link using a standard web browser your visit will be handled like if you visited the /html/ version of the link. Applications expecting rdf should still get the same result as before. /André Costa (WMSE) (talk) 12:43, 1 December 2020 (UTC)

I asked RAÄ helpdesk why its so complicated to understand P1260 from Fornsök

See answer in Swedish helpdesk question I-2206-0290 (video in Swedish with the question)

Alternativ länka direkt till objektet i källsystemet hos Riksantikvarieämbetet - Fornsök

Man kan länka direkt till objektet i Riksantikvarieämbetets källsystem, Fornsök, om man så önskar. Enklast är då att söka upp objektet i fråga som man vill länka till i Fornsök. Det finns ett antal sökmöjligheter tillgängliga, t ex via kartan eller via sökning per attribut. När man hittat objektet i fråga i Fornsök kan man få en länk till objektet i fråga i syfte att användas av en människa i en webbläsare. Enklaste sättet är att göra som du gjorde i videon, dvs klicka på "Dela" knappen i Fornsök och använda den länken du får genererad där. I det här fallet länken: https://pub.raa.se/visa/objekt/lamning/6831c172-c408-4e04-aa25-75c0cc193c98

Kommentarer till "ska det vara så här komplicerat" I videon du bifogade ställs frågan "ska det vara så här komplicerat". Svaret är att givetvis nej, så komplicerat ska det naturligtvis inte vara.

Några kommentarer till de moment som beskrivs i videon. I videon du bifogade verkar det som att du själv försöker återskapa en länk (upplösningsbar URI) utställd av K-samsök ("http://kulturarvsdata.se/raa/fmi/10008703000001" ) istället för att använda den länk som aggregatorn K-samsök genererar för objektet i fråga. Som användare varken ska eller förväntas du behöva känna till hur K-samsök genererar en länk till ett givet objekt. I det här fallet blir det dessutom felaktigt då K-samsök numera genererar länkar i ett annat format än det du försöker återskapa. Det framgår både i såväl söktjänsten kringla som i den tekniska http responsen (headers) man får om man konsumerar länken ovan. Rekommendationen här är att använda den länk som aggregatorn genererar. I videon följer du en länk för en lämning ifrån systemet "Fornsök" och hamnar då i en annan söktjänst från Riksantikvarieämbetet - "Arkivsök". Arkivsök är en söktjänst för arkiverad dokumentation hos Riksantikvarieämbetet. Metadatan som du sedan laddar ned från Arkivsök är metadata som beskriver dokumentationsposter som finns för lämningen - i Arkivsök. I det här fallet råkar attributet "fmis_id" finnas även här eftersom dokumentation beskriver samma lämning du är intresserad av - men du är nu i fel system (Arkivsök) och använder fel metadata (metadata för dokumentationsposten) i ett dataformat (JSON) avsett att konsumeras av maskiner än för den lämning du avsåg i Fornsök. F.k- attributet "fmis_id" var en intern teknisk identitet från systemet FMIS som fanns på Riksantikvarieämbetet och som lades ned för ett antal år sedan. Alla objekt har inte något sådant attribut - eftersom vissa poster uppstått efter att FMIS avvecklades. Vi kan inte nog varmt rekommendera dig att under inga omständigheter överhuvudtaget alls använda dig av det attributet längre. Vi noterade även att Wikidatasidan även använder sig av attributet RAÄ-nummer. RAÄ-nummer var en annan (icke-unik) identitet avsedd att användas för människor (en s.k. människoläsbar identitet) för en lämning i det nu nedlagda systemet FMIS. Även här är det så att alla objekt inte har attributet RAÄ-nummer - eftersom vissa poster uppstått efter det att FMIS avvecklades.

För kännedom så finns en motsvarande "människoläsbar" identitet i dagens Fornsök avsedd att användas av människor - attributet lämningsnummer. Lämningsnummer finns för alla lämningar och är dessutom unika.

• I exemplet du använder ingår lämningsnumret i rubriken: "L2015:4648"

My understanding is that we need a new WD property Lämningsnummer?!?!?! - Salgo60 (talk) 05:27, 16 June 2022 (UTC)

Added comment on RAÄ number (P1262) mentioned in the answer above see link and also on sv:Wikipedia page Bybrunnen- Salgo60 (talk) 06:09, 16 June 2022 (UTC)