Användare:Tommy Kronkvist

<mediawiki xmlns="http://www.mediawiki.org/xml/export-0.11/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mediawiki.org/xml/export-0.11/ http://www.mediawiki.org/xml/export-0.11.xsd" version="0.11" xml:lang="sv">
  <siteinfo>
    <sitename>Wikimedia</sitename>
    <dbname>sewikimedia</dbname>
    <base>https://se.wikimedia.org/wiki/Huvudsida</base>
    <generator>MediaWiki 1.47.0-wmf.12</generator>
    <case>first-letter</case>
    <namespaces>
      <namespace key="-2" case="first-letter">Media</namespace>
      <namespace key="-1" case="first-letter">Special</namespace>
      <namespace key="0" case="first-letter" />
      <namespace key="1" case="first-letter">Diskussion</namespace>
      <namespace key="2" case="first-letter">Användare</namespace>
      <namespace key="3" case="first-letter">Användardiskussion</namespace>
      <namespace key="4" case="first-letter">Wikimedia</namespace>
      <namespace key="5" case="first-letter">Wikimediadiskussion</namespace>
      <namespace key="6" case="first-letter">Fil</namespace>
      <namespace key="7" case="first-letter">Fildiskussion</namespace>
      <namespace key="8" case="first-letter">MediaWiki</namespace>
      <namespace key="9" case="first-letter">MediaWiki-diskussion</namespace>
      <namespace key="10" case="first-letter">Mall</namespace>
      <namespace key="11" case="first-letter">Malldiskussion</namespace>
      <namespace key="12" case="first-letter">Hjälp</namespace>
      <namespace key="13" case="first-letter">Hjälpdiskussion</namespace>
      <namespace key="14" case="first-letter">Kategori</namespace>
      <namespace key="15" case="first-letter">Kategoridiskussion</namespace>
      <namespace key="90" case="first-letter">Tråd</namespace>
      <namespace key="91" case="first-letter">Tråddiskussion</namespace>
      <namespace key="92" case="first-letter">Summering</namespace>
      <namespace key="93" case="first-letter">Summeringsdiskussion</namespace>
      <namespace key="100" case="first-letter">Projekt</namespace>
      <namespace key="101" case="first-letter">Projektdiskussion</namespace>
      <namespace key="710" case="first-letter">TimedText</namespace>
      <namespace key="711" case="first-letter">TimedText talk</namespace>
      <namespace key="828" case="first-letter">Modul</namespace>
      <namespace key="829" case="first-letter">Moduldiskussion</namespace>
      <namespace key="1198" case="first-letter">Translations</namespace>
      <namespace key="1199" case="first-letter">Translations talk</namespace>
      <namespace key="2600" case="first-letter">Ämne</namespace>
    </namespaces>
  </siteinfo>
  <page>
    <title>Användare:Tommy Kronkvist</title>
    <ns>2</ns>
    <id>3223</id>
    <revision>
      <id>136842</id>
      <parentid>136835</parentid>
      <timestamp>2026-07-27T12:39:54Z</timestamp>
      <contributor>
        <username>Tommy Kronkvist</username>
        <id>63</id>
      </contributor>
      <comment>Uppdaterade användardata.</comment>
      <origin>136842</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3946" sha1="7jih3c7gulfd1emmxpqstv982cd4ims" xml:space="preserve">[[Fil:Tommy Kronkvist.jpg|mini|240px|Undertecknad, nyårsafton 2007.]]
{{#Babel:sv|en-4|de-2}}

Jag heter '''Tommy Kronkvist''' och är betalande medlem i föreningen Wikimedia Sverige sedan i april 2019. Jag bor i Uppsala och bidrar till en rad olika Wikimediaprojekt under samma användarnamn som här. Jag registrerade mig i wiki-gemenskapen 29 mars 2005 och har sedan dess hunnit med lite drygt '''399&amp;nbsp;300''' redigeringar i de 153 olika Wikimedia-projekt jag bidragit till (per 27&amp;nbsp;juli&amp;nbsp;2026). Mitt användarkonto är registrerat i ytterligare 265 Wikimedia&amp;shy;projekt som jag till dags dato dock inte bidragit till: främst för att jag ännu inte hunnit lära mig maori, uzbekiska, malagassiska och en hel hop andra &lt;span style=&quot;white-space:nowrap&quot;&gt;språk. [[Fil:Face-smile.svg|18px|link=]]&lt;/span&gt; För detaljer om rubb och stubb, se '''[[meta:Special:CentralAuth/Tommy Kronkvist|min globala kontoinformation]]''' på Meta-Wiki. Notera dock att den databasen byggdes om i augusti 2008 så registrerings&amp;shy;datumen är ungefär tre och ett halvt år fel (i förhållande till 2005, när jag registrerade mitt konto ''de facto''). Tittar man i historiken för de enskilda wikiarna så hittar så hittar man dock korrekt anslutningsdatum för respektive projekt.

Sedan juni 2021 är jag administratör här på Wikimedia Sverige.&lt;small&gt;&lt;sup&gt;&lt;span class=&quot;plainlinks&quot;&gt;[{{fullurl:Special:Användare|limit=1&amp;username={{PAGENAMEE}} (verifiera)}}]&lt;/span&gt;&lt;/sup&gt;&lt;/small&gt; Jag är emellertid sedan länge främst aktiv på Wikispecies&lt;small&gt;&lt;sup&gt;([[species:User:Tommy Kronkvist|användarsida]])&lt;/sup&gt;&lt;/small&gt; i egenskap av administratör, byråkrat och gränssnittsadministratör,&lt;small&gt;&lt;sup&gt;&lt;span class=&quot;plainlinks&quot;&gt;[https://species.wikimedia.org/w/index.php?title=Special:ListUsers&amp;limit=1&amp;username=Tommy_Kronkvist (verifiera)]&lt;/span&gt;&lt;/sup&gt;&lt;/small&gt; samt på svenska Wikivoyage&lt;small&gt;&lt;sup&gt;([[voy:Användare:Tommy Kronkvist|användarsida]])&lt;/sup&gt;&lt;/small&gt; där jag är administratör och gränssnittsadministratör.&lt;small&gt;&lt;sup&gt;(&lt;span class=&quot;plainlinks&quot;&gt;[https://sv.wikivoyage.org/w/index.php?title=Special:ListUsers&amp;limit=1&amp;username=Tommy_Kronkvist verifiera])&lt;/span&gt;&lt;/sup&gt;&lt;/small&gt; Jag är också ensam ansvarig för &lt;span class=&quot;plainlinks&quot;&gt;[https://twitter.com/Wikispecies @Wikispecies]&lt;/span&gt; officiella X-konto (tidigare kallat Twitter) samt har registrerat ett konto på &lt;span style=&quot;white-space:nowrap&quot;&gt;Phabricator,&lt;small&gt;&lt;sup&gt;([[phab:p/Tommy Kronkvist|användarsida]])&lt;/sup&gt;&lt;/small&gt;&lt;/span&gt; ett projekthanteringssystem för samarbete kring utveckling av wiki-mjukvara.

Om du vill skicka signerad och/eller krypterad e-post till mig så hittar du min publika PGP-nyckel här: [[species:User:Tommy Kronkvist/PGP|19035D3D]]. Okrypterad, &quot;vanlig&quot; mejl går naturligtvis också bra, men är förstås inte lika säker. Vill du skicka mejl till mig med hjälp av Wikimedias egen epost-tjänst (utan PGP), så kan använda [[Special:E-post/Tommy Kronkvist|det här formuläret]].
{{Clear}}
{| class=&quot;toccolours&quot; style=&quot;cellpadding=4;&quot;
| style=&quot;background: #ccf; text-align: center; padding-right: 0.4em; width: 20%; font-size: 0.8em;&quot; | SHA-512 [[meta:Template:User committed identity|Committed identity]] hash: 
| style=&quot;background: #e0e8ff; text-align: left; padding-right: 0.4em; padding-left: 0.4em; font-size: 0.8em;&quot; | a6edd6d2fdbf82621f0cda4e5525c71f8da9b5dfd308242c3c63365e998c32c5406b75448380903265a5403edffd1a0435b61ac943f3c65870db9250f8b884a9
|-
| width=&quot;300&quot; style=&quot;background: #ccf; text-align: right; padding-top: 0.3em; padding-right: 0.4em; padding-bottom: 0.3em; width: 15%; font-size: 0.8em;&quot; | Min publika [[w:Pretty Good Privacy|PGP]]-nyckel: 
| style=&quot;background: #e0e8ff; font-size: 0.8em;&quot; | &amp;nbsp;[[species:User:Tommy Kronkvist/PGP|19035D3D]]. Använd den gärna om du kontaktar mig via e-post. Vanlig okrypterad e-post går naturligtvis också bra, men är förstås inte lika säker.
|}

[[Kategori:Användare]]</text>
      <sha1>7jih3c7gulfd1emmxpqstv982cd4ims</sha1>
    </revision>
  </page>
  <page>
    <title>Checklista för avslutande av anställning</title>
    <ns>0</ns>
    <id>5568</id>
    <revision>
      <id>136843</id>
      <parentid>121738</parentid>
      <timestamp>2026-07-28T07:16:41Z</timestamp>
      <contributor>
        <username>Sebastian Berlin (WMSE)</username>
        <id>2598</id>
      </contributor>
      <comment>Flytta punkt om telefon till organisationsassistent.</comment>
      <origin>136843</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="6561" sha1="7f4v5bwjg4u6gxuwp0coq27zx6daakf" xml:space="preserve">&lt;noinclude&gt;
:Använd &lt;code&gt;&lt;nowiki&gt;{{subst::Checklista för avslutande av anställning}}&lt;/nowiki&gt;&lt;/code&gt; (med två kolon) för att skapa denna lista på en undersida.
__TOC__
&lt;/noinclude&gt;

== Innan sista arbetsdagen ==

=== Den anställda ===

*{{Kryssruta|}}Flytta över alla dokument som finns lokalt på datorn, eller i &quot;min enhet&quot; i Google Drive till en lämplig Team Drive mapp i Drive.
*{{Kryssruta|}}Ladda ner lönespecifikationer och annat lönerelaterat om du vill att dessa inte ska försvinna. De hittas på Fortnox. 
**Det kan vara viktigt att spara lönebesked ett tag då man i kontakt med vissa myndigheter/instanser kan behöva uppgifterna som finns i ett lönebesked.
***Exempelvis om man ska ändra inkomstuppgifter hos Försäkringskassan så går handläggningen snabbare om man kan visa ett lönebesked. 
***Skatteverket har enligt lag rätt att korrigera/ändra någons beskattning 6 år bakåt. Skulle man hamna i någon tvist med Skatteverket så är det bra att kunna bevisa hur mycket skatt arbetsgivaren har innehållit (OBS det här är förhoppningsvis ett '''väldigt ovanligt''' fall). 
***A-kassan kan efterfråga lönebesked. 
*{{Kryssruta|}}Se till att alla öppna tasks i Phabricator stängs eller flyttas över till nya ansvariga. Gäller både assigned/claimed tasks och de på den personliga workboarden.
*{{Kryssruta|}}Ändra kontaktperson på de frivilligmallar som syns på [[Frivilliguppdrag]]. (Till ny projektledare för det projektet)
*{{Kryssruta|}}Be Tranås resebyrå rensa eventuell inlämnad resenärsprofil.
*{{Kryssruta|}}Se över om särskilda behörigheter på användarkonton (exempelvis kurser i [[wmfdashboard:|Programs and Events Dashboard]]) behöver överföras till annan anställd.
*{{Kryssruta|}}Töm [[:Kategori:Ledningsrapporter-FÖRNAMN]]
*{{Kryssruta|}}Inaktivera två-faktor autentisering i Mailchimp och peka om kontot till info{{@}}wikimedia.se.

== Sista arbetsdagen ==

=== Den anställda ===
*{{Kryssruta|}}Ställ in autosvar på mailen eller omdirigera till annan anställd/info.
*{{Kryssruta|}}Lämna Kontorschatarna
*{{Kryssruta|}}Se över om särskilda behörigheter på användarkonton (exempelvis kurser i Programs and Events Dashboard) behöver överföras till annan anställd.
*{{Kryssruta|}}Uppdatera användarsidor på alla wikiprojekt, till exempel genom att uppdatera [[m:special:MyPage användarsidan på Meta]] och begära radering av alla lokala sidor.

=== Med tekniker ===

*{{Kryssruta|}}Ta in dator. 
**{{Kryssruta|}}Ominstallera datorn med senaste Ubuntu LTS så att den är redo för ny användare.
*{{Kryssruta|}}Inaktivera Phabricator, om den anställdas konto är kopplat till ett WMSE-wikimedia-konto
**{{Kryssruta|}}Arkivera &lt;code&gt;User-*&lt;/code&gt; projektet
**{{Kryssruta|}}Inaktivera kontot m.h.a. [https://phab-ban.toolforge.org/ Phab ban]

=== Med organisationsassistent ===

*{{Kryssruta|}}Ta in telefon och återställ den
*{{Kryssruta|}}Uppdatera abonnemang
**{{Kryssruta|}}Kontrollera om telefonnumret behöver pausas eller avslutas
**{{Kryssruta|}}Återställ lösenord och pinkod i [https://tele2vaxel.se växeln] (0200-232323)
**{{Kryssruta|}}Vidarebefordra samtal till växeln (0200-232323).
*{{Kryssruta|}}Ta in eventuell övrig utrustning
*{{Kryssruta|}}Ta in [[Betalkortspolicy|betalkort]] och ta bort personen i banken

=== Med kontorsansvarig ===

*{{Kryssruta|}}Ta in nycklar

=== Med verksamhetschef ===

*{{Kryssruta|}}Fika och avskedspresent

== Efter avslutad anställning ==

=== Organisationsassistent ===

* Informera Opad om att den anställda har slutat. 
**{{Kryssruta|}}Ändra behörighet i ekonomisystem
**{{Kryssruta|}}Se till att uppgifter om den anställda uppdateras hos Collectum (syns på faktura). Först efter att en anställds slutlön är utbetald kan personen avregistreras från Collectum, kreditering sker om för mycket har betalats in till Collectum. (Fora är inte individbaserat, där rapporteras endast bruttolön för året in, dvs ingen avanmälan behövs).
*{{Kryssruta|}}Kontakta Folksam och meddela att den anställda inte längre ska omfattas av organisationens olycksfallsförsäkring.
*{{Kryssruta|}}Ta bort eventuell behörighet att boka resor med Wikimedia Sveriges företagskonto hos SJ.
*{{Kryssruta|}}Ta bort behörighet från [https://wikimedia.se Bloggen och hemsidan] (ändra till &lt;code&gt;bidragsgivare&lt;/code&gt; eller &lt;code&gt;prenumerant&lt;/code&gt;)
*{{Kryssruta|}}Om person har haft behörighet till Scrive, ladda ner eventuella kvarvarande dokument till drive innan konto stängs ned. 
*{{Kryssruta|}}Ta bort eventuell behörighet i Scrive.
*{{Kryssruta|}}Ta bort eventuell behörigheter på kurser i LearnWiki.

=== Tekniker ===

*{{Kryssruta|}}Avaktivera Google Workspace-konto
**{{Kryssruta|}}Lägg till vidarebefordran av wikimedia.se-mejladress om så önskas
**{{Kryssruta|}}ELLER lägg till [[Autosvar för gammal mejladress|autosvar]].
**{{Kryssruta|}}Ta bort kontot från grupper, för att undvika att mejl vidarebefordras
**{{Kryssruta|}}Ändra eventuella omdirigeringar för e-post i Google Workspace (t.ex. jobb{{@}}wikimedia.se, kolla samtliga funktionsadresser under [https://admin.google.com/ac/apps/gmail/routing routing])
**{{Kryssruta|}}Ändra eventuella ägandeskap av grupper
*{{Kryssruta|}}Ta bort eventuell behörighet i Github
*{{Kryssruta|}}Ta bort eventuell behörighet i Loopia (bankid)
*{{Kryssruta|}}Ändra ansvarig på [[Wikimedia:Mediawiki Extension Policy]] (om ED eller COO)

=== Kontorsansvarig ===

*{{Kryssruta|}} Ändra behörighet i föreningswikin
*{{Kryssruta|}} Ta bort personen på [[Funktionärer]] samt [[w:sv:Wikipedia:Wikimedia Sverige]].
*{{Kryssruta|}} Se över och ändra eventuell behörighet på Twitter, Instagram, LinkedIn och Facebook.
*{{Kryssruta|}} Kategorisera om användarsidor och eventuell [[c:Category:Wikimedia_Sverige_staff|commonskategori]] till tidigare/former.

=== Verksamhetschef ===

*{{Kryssruta|}}Ta bort eventuell behörighet i banker/Paypal
*{{Kryssruta|}}Se till att slutlön betalas ut
*{{Kryssruta|}}Ta bort information om anhöriga
*{{Kryssruta|}}Ta bort eventuell behörighet i Firmateckningsordningen
*{{Kryssruta|}}Markera användaren som inaktiv i Fortnox.&lt;!--OBS: Ska ej ske innan slutlönen är färdig. 
 Administrera användare-&gt;klicka på namnet-&gt;aktiv=nej --&gt;

== Noter ==
&lt;references/&gt;

&lt;includeonly&gt;[[Kategori:Checklistor {{subst:&lt;noinclude&gt;&lt;/noinclude&gt;CURRENTYEAR}}]]
[[Kategori:Oavklarade checklistor]]&lt;/includeonly&gt;
&lt;noinclude&gt;
[[Kategori:Checklistor|Avslutande av anställning]]

[[Kategori:Personal| ]]
&lt;/noinclude&gt;</text>
      <sha1>7f4v5bwjg4u6gxuwp0coq27zx6daakf</sha1>
    </revision>
  </page>
  <page>
    <title>Projekt:CommonsDB registry/Implementation</title>
    <ns>100</ns>
    <id>28508</id>
    <revision>
      <id>136844</id>
      <parentid>136838</parentid>
      <timestamp>2026-07-28T10:21:28Z</timestamp>
      <contributor>
        <username>Ainali</username>
        <id>5</id>
      </contributor>
      <comment>/* Declaring new uploads to the registry */ viewpoints from the Wikimania workshop</comment>
      <origin>136844</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="18551" sha1="p8urrcekf1bw4vv9eaxsgfki6imjiyq" xml:space="preserve">[[File:CommonsDB introduction.webm|thumb|200px|Explainer video of CommonsDB.]]
On this page we collect ideas, thoughts and considerations on how [[m:CommonsDB/Potential for the communities|the potential]] could be realized and what requirements that will have on the Wikimedia infrastructure. Some of the ideas are visualized on a high level in the video to the right. For now, all info goes on this page, but eventually they may need separate subpages.

== Checking if a new upload already is in CommonsDB ==
Note that the ways this could be implemented may vary depending on with which method an image is being uploaded. The UploadWizard may be the main way to implement it, as most of the other tools have either very experienced users (like OpenRefine users) with better than average knowledge about copyright, or (like the Wikimedia Commons app) mainly feature uploading original content. However, considering that there are many tools that can be used to upload to Wikimedia Commons, and that some tool developers wants to benefit from more features and make their uploads have as high quality as possible too, it might be worth considering the design of the feature to be generic and reusable through an API or library that can enable tools to use this functionality as a service.

=== UploadWizard ===

==== Check the CommonsDB register ====
# After media has been uploaded in the browser, an ISCC code can be generated for each of the submitted files.
# Use the ISCC for each of them to query the CommonsDB register to see if it is known.
## If assets with exact match or very high similarity is found, suggest a license template/statement based on the result (see below), possibly with a link so that the user can explore/verify.
### If the asset was supplied by Wikimedia, instead show a text like &quot;There is already a similar file on Wikimedia Commons. Only upload your file if you are sure it is adding value.&quot; and link to the asset.
### If it was an exact match (bit distance 0) and it didn't come from Wikimedia, suggest using the CommonsDB source link in the UploadWizard Source field. 
## If assets with high similarity is found, provide a link so that the user can explore/verify and if it was a match suggest a license template/statement based on the result.
## If it is not, do nothing.

All through this, log which message that was shown and what action user took (did they abort the upload or did they continue, and if so, with the license we showed or some else?).

==== Selecting license templates ====
When checking for similar matches as described above, if a match is found the rights statement of that asset can be used to select the right license on Wikimedia Commons. One way could be to match the string to an item on Wikidata with that value in official website (P856) and then from that item find topic has template (P1424) and get the Commons sitelink from that value, which should be the correct template. Of course, this need to be verified for all allowed rights statements in the registry, taking particular care of public domain which may be modeled differently on Commons. Possibly for performance reasons, we could make this a cached table and not query for this each time as the values are unlikely to change very often, if at all.

Example: If the CommonsDB register says that the image has the license:
* https://creativecommons.org/licenses/by-sa/2.5/it/ 
we can query the Wikidata API with the a question like this: 
* https://www.wikidata.org/w/api.php?action=query&amp;format=json&amp;generator=search&amp;formatversion=2&amp;gsrsearch=haswbstatement%3AP856%3Dhttps%3A%2F%2Fcreativecommons.org%2Flicenses%2Fby-sa%2F2.5%2Fit%2F
This gives us the item Q98929925, from which we can again query which template this license is using through a query like:
* https://www.wikidata.org/w/api.php?action=wbgetclaims&amp;format=json&amp;entity=Q98929925&amp;property=P1424&amp;formatversion=2
This gives the item Q15304563 from which we can get the template name with:
* https://www.wikidata.org/w/api.php?action=wbgetentities&amp;format=json&amp;ids=Q15304563&amp;languages=en&amp;formatversion=2
which finds the name of the template on Commons in the sitelinks section, [[c:Template:Cc-by-sa-2.5-it|Template:Cc-by-sa-2.5-it]]. This can be suggested for the user as suitable license template. The last two bullet points can also be done by a single PSARQL query, provided that all items in step one is used as values for it, like this: https://query-chest.toolforge.org/redirect/WzZyyJjus4wYSo2IUm0UMAMKY4AoqwOs6oE0o0uAWeg

Note that for images in the public domain we will need the PD Rationale to pick a good license on Commons as they have so many public domain templates to choose from. If that is not available, I think our best action is just to say that CommonsDB thinks this is in the public domain and leave it up to the user to pick the correct template.

Note that these values are unlikely to change very often, so instead of doing these API calls every time, it might be better to make a static lookup table where we get the template text for each canonical license URL. A table for this is at [[Projekt:CommonsDB registry/Implementation/License URL to license template|License URL to license template page]].

Since the license selection comes on the next page in the upload workflow, we likely need to carry the information over there, especially for the case when the user is uploading multiple images having different licenses in CommonsDB.

==== Store ISCC ====
The ISCC code should be stored as Structured Data: there is already a property for this, {{P|P13150}}. This should be possibly qualified with Wikimedia page-version URL (P7569) so that it is clear which uploaded file the ISCC is for.

=== Prototyping options ===
[[Fil:CommonsDB Wikimedia Nortwestern Europe hackathon - showcase video.webm|miniatyr|Demo of a user script generating an ISCC code and then checking the CommonsDB registry.]]
An alternate workflow where a user uploads to a tool on Toolforge could be created, where that tool generates the ISCC, does the check against the CommonsDB API and recommends a licensing template based on the result. Then it either makes the upload completely separately or forwards the information to the UploadWizard.

A bit more integrated workflow, would be to create a user script. This one could then &quot;embed&quot; itself in the regular workflow, and don't feel that different for the user. Possibly, parts of the work behind the scenes could still benefit of a tool on Toolforge to generate the ISCC.

The first option is likely easier to build, whereas the second one would be a more convincing demo for the end user. It might also make it more clear for WMF developers on exactly where in the upload process the tool could be integrated.

=== Final implementation ===
Since the search API for the CommonsDB registry needs an API key that shouldn't be shared, a gadget or user script is not really possible as the key would be visible to anyone. At the same time, it need to be investigated what requirements comes along due to the fact that this is a service that neither is in the Wikimedia ecosystem, nor open source. Likely, we need configuration for the user, possibly even being opt-in with a clear message about the nature of the API.

== Declaring new uploads to the registry ==

We probably want some kind of a &quot;grace period&quot;  before we declare a new upload to the registry which can be differentiated by the user group of the uploader. Furthermore, we can take in account positive (reviewed licenses, EXIF data matching license choice, reuse of images) and negative (mismatch between EXIF and license, other metadata corruption, deletion tags) signals to either clear or delay the declaration. This period and additional checks will allow for poor uploads to be speedily deleted and for some of the most common bots to add metadata in structured form to the file (examples: [https://commons.wikimedia.org/w/index.php?title=File%3ACecropia_telenitida_448681395.jpg&amp;diff=1101917792&amp;oldid=1101059604 SchlurcherBot], [https://commons.wikimedia.org/w/index.php?title=File:Hamr%C3%A5ngefj%C3%A4rden_20250822_165319.jpg&amp;diff=prev&amp;oldid=1081728006 BotMultichillT]) The length of this period should be checked with the community and be long enough so that the bots would be likely to have added the metadata to it and therefore minimize the need for updating declarations.

After the period has passed an upload can be considered as stable enough and a declaration should be made.

=== Store declaration status ===
That a declaration has been made should be stored somewhere, possibly as Structured Data. Storing the Declaration-ID as a main statement will make it easy to query for, and also makes sense as it is a kind of external identifier. Optionally, there could also be a qualifier on either the ISCC statement or this, connecting the two to each other (so that it is clear that the ISCC gave cause to the declaration ID). Declaration-ID can be used to lookup the CommonsDB API returning a JSON file. Example: https://api.commonsdb.org/v1/metadata-pub/bbqjcaww2wlkm5lnswq6rmsejzxnscz3ynvyvly2o2pnanrjxng3yftpb

=== Prototyping options ===
This could be built as a prototype on Toolforge. It could be done in a couple of steps. The first step is to identify suitable images to declare, generate the ISCC and put them in a queue. The second step, which we can enable when we feel like the first step is stable enough, is to do the declaration. The third step is to store the declaration status and ISCC on toolforge in a way that can be seen and show a suggested edit to Wikimedia Commons. When the needed properties have been created, those edits could be made to the file.

== Updating metadata in the registry ==
Sometimes when the information on the file page or its structured data is updated, this is information that could be updated to the original declaration. In particular, changes of the license should be of important to update.

It seems nontrivial to detect changes like this and some service that looks for that sort of changes may be needed.

=== Prototyping options ===
Here we could experiment with a toolforge tool scanning the recent changes on Commons, trying to detect relevant changes (like removing a Creative Commons template and adding a public domain template) on already declared images. In a first step, just finding the relevant changes is the goal and make it possible/easy for us to see how well the detection works. Making a new declaration can be made either after human review, or when we are confident that the detection is good enough. 

== Navigating to the registry ==
Files that have declaration ID or that have an ISCC code in the structured data could have a link to the registry to either see what is stored there or if someone else has declared the file.

=== Prototyping options ===

* [[c:User:Ainali/commonsdb-link.js|A user script t]]&lt;nowiki/&gt;hat checks if a file has an ISCC code and adds a link to CommonsDB explorer if it does. (Add by editing [[c:Special:MyPage/common.js|your common.js]] page like [https://commons.wikimedia.org/w/index.php?title=User:Ainali/common.js&amp;diff=1151171313&amp;oldid=1035432594 this].)
* Similarly, a user script could be created for the declaration ID once we have that property.
* We could also make a template that adds the link. We could both have a generic template that as a parameter takes an ISCC code and then displays it alongside links to the registry and possibly also other services. If the template is used on an image page that has an ISCC code, one wouldn't even need to add it as a parameter (and doing so could override it). Additionally, if such a template is working well, it could be integrated into the Information templates on Commons.

=== Final implementation ===
When there is enough files declared in the registry and their ISCC codes has been added as structured data, evolving the user script into a gadget is probably a good first step. However, best scalability is probably through the template and integrating it to existing information templates.

== Removing(?) declarations of deleted files from the registry ==
If a file gets removed from Wikimedia Commons, the registry should be updated or possibly have the entry removed.

Here, we probably need a tool that listen to the [[wikitech:Event Platform/EventStreams HTTP Service|EventStreams]] on the [https://stream.wikimedia.org/v2/ui/#/?streams=mediawiki.page-delete mediawiki.page-delete stream] and check every deleted page against our database of declared files and if we find a match, we should start the process of updating CommonsDB with this information. (That process is still to be decided, but likely a declaration with some specific value or status.)

== Find duplicates among existing images ==

This would, in theory, be a one-time job of checking all images on Commons with the property ISCC against each other to see if there are duplicates. (In theory because it is unlikely we ever will be fully caught up due to new uploads with alternative uploads not checking for duplicates with ISCC.) It is likely that we do want some images that are very similar to each other, whereas others may have been mistakes of different kinds. For the mistakes, the community can decide if they want to delete the &quot;duplicate&quot; images (perhaps including redirects). For the ones that should be kept, a way to mark this as intentional would be good. Possibly this could be done with the other versions field in the Information template. Then, files linking to each other using the Other versions field can be excluded from being marked as a duplicate automatically as they have already been properly dealt with. (Obviously, we can find a further versions which would then would need to be dealt with.)

=== Prototyping options ===
This is probably easiest done as a tool on Toolforge (which likely also is the final form). The tool consists of two parts, a script and a graphical interface. 

The script will be making a query to get all images with ISCC in the structured data periodically to fill a list of files to check (it will need to be periodically as new images are added to Commons continuously). Each of these would then be looked up in CommonsDB. Those that have no hits at all can be marked as unique. 

All others go into a queue for human review in the graphical interface (which is available as a page on Toolforge). Users are then presented by an image and can mark it for action or as a false positive which then just remove it from the review queue. Possible actions can be &quot;tag for deletion as duplicate&quot;, &quot;keep, but link in Other versions&quot;, &quot;keep but no edit&quot; or &quot;skip&quot;. All but the last should also remove it from the queue. 

=== Suggesting category improvements ===

This is a similar one-time job for all of the images that are kept. It is likely that similar images should have at least one category in common, so a tool to easily make these edits could be made. This is likely a good &quot;game&quot; where users just approve or reject suggestions. If the user decides there should be no category in common, this may be odd to store on the files, which also suggests that an external tool can be useful.

== Find higher resolutions of images already on Commons ==
If we find matches in CommonsDB from another data provider, we can check their source to see if they have a file with higher resolution than the one on Commons.

== Find duplicates when preparing a batch upload ==
When doing batch uploads from GLAM partners, it [[w:sv:Wikipedia:Bybrunnen#c-Salgo60-20260315142800-Alicia_Fagerving_(WMSE)-20260313120300|may help]] to generate the ISCC codes pre-upload and check the files to see if there are any potential duplicates to prevent them ''before'' the upload. This may be helpful for regular users too, to avoid uploading an entire folder where there are some &quot;burst shots&quot; where a manual selection would be better.

=== Prototyping options ===
A local script (or app) that generates ISCC codes for a set of images and then just checks the similarity between them. The script could order the most similar images for manual review.

== Integrating in external tool workflows ==
For small GLAMs, adding requirements of extra checks that has to be done can feel burdensome. Therefore, it would be great if existing tools could be enhanced to help out. For example. could there be an extension to OpenRefine that for images in a loaded project both calculated the ISCC (which then could be submitted as structured data) and compared them to each other. 

== Find media that has entered the public domain since the upload ==

This is not really related to the ISCC as such, but as we have declared and signed the metadata, we should make efforts to have that data be accurate. In the best of worlds, the community is already on top of this and we would just follow the process for updating the metadata in the registry as described above. However, no tools that assist such workflows are known and may be helpful for the community. A small subset, where the author of the file has a Wikidata item, could be discovered through a SPARQL query, by checking if enough time passed since the author died. This can create a queue for human review as it is might not be possible to determine the exact legal conditions for each image as it varies so much per jurisdiction.

== Resolve externally found &quot;conflicts&quot; ==
Here there are two scenarios, an initial check and then a continuous queue.

=== Initial check ===
This would be a one-time job of checking all images on Commons against other files in the registry. Files with exact match or very high similarity and a mismatch with the rights statement and the license on the file should be put in a queue for human review. Likely some manual investigation is needed to understand why this conflict occurred. Then, either the license is changed, or it should be marked as having the right one, possibly triggering a notification to the other data provider.

=== Continuous queue ===
Whenever new files are declared in the registry by other data providers that have exact or high similarity with files on Commons but where the rights statement are not the same, we should have a way to receive that notification and investigate the file. This could be a VRT queue if it needs to be email, but it would be better with a public list onwiki that anyone could help check. For this a bot receiving the notification could trigger an edit to add something to that list.
[[Kategori:CommonsDB registry|Implementation]]</text>
      <sha1>p8urrcekf1bw4vv9eaxsgfki6imjiyq</sha1>
    </revision>
  </page>
</mediawiki>