The Library Data uploads will need edit summaries with a "hash tag" so that we can easily collect data about them. Probably something like:
#WMSE #LibraryData or #WMSE #LibraryDataKB or #WMSE #LibraryData #KB
#WMSE #Biblioteksdata
Adding KB means we don't run the risk of clashing with a possible other library data batch, if it even exists.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Alicia_Fagerving_WMSE | T202527 Process and upload the Libris authorities database | |||
| Resolved | Alicia_Fagerving_WMSE | T202396 Mass upload of Libris URI's | |||
| Resolved | Alicia_Fagerving_WMSE | T202398 Test upload of Libris URI's | |||
| Resolved | Alicia_Fagerving_WMSE | T202392 Edit summaries for Library Data uploads |
@Lokal_Profil After sleeping on this crucial issue I think #WMSE #LibraryData-KB makes most sense.
IIRC hyphens don't work in hashtags on most platforms. Underscores do but are not commonly used.
@Lokal_Profil Then without the hyphen…
#WMSE #LibraryData_KB?
I think there's a benefit to adding KB to make it more unique.
Is that more clear than #WMSE #LibraryDataKB?
I agree that adding KB makes sense so this is essentially just bikeshedding
It's a personal preference (more readable visually) but I don't really have other arguments…