Esc3300 added a comment.

[..]

  • 3. Splitting the property into multiple properties

also: * CONS can't cover use cases like ISIL
also: * CONS leads to an indefinite number of properties for basic uses like catalog codes

  • 4. Wikibase provides list of predefined generic transformations, which then somehow set for each external identifier property individually (for example, as classifiers for formatter URL property) and applied to value on render.
    • CONS Will have some super specific transformations (like "IMDB id transformation" and "CricketArchive ID transformation", because URL generation algorithms are very specific)

Maybe it's just matter of coding. It doesn't need to be done in the same way as on tools.wmflabs.org/wikidata-externalid-url

  • 7. Use regex with capturing groups as qualifier and replace $ variables in formatter URL accordingly (ex.: (\d{2})-(\d{4}) and http://www.bls.gov/soc/2010/soc$2$3.htm)
    • CONS Does not cover all the current cases (ex.: IMDB, HURDAT, ZVG, CricketArchive)

I'm not really an expert on regex either, but regexes for IMDb were already available before the current exernal-id solution. Maybe it's just a matter of implementing this correctly.

  • 8. Use Lua code as property's property to define formatter function (as a raw code or a module reference).

also: * CONS Have to be supported by developers


TASK DETAIL
https://phabricator.wikimedia.org/T151329

EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Aleksey_WMDE, Esc3300
Cc: Glorian_WD, WMDE-leszek, Mbch331, Aleksey_WMDE, thiemowmde, Pasleim, Esc3300, Aklapper, Stigmj, Nikki, hoo, Lydia_Pintscher, D3r1ck01, Izno, Wikidata-bugs, aude
_______________________________________________
Wikidata-bugs mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Reply via email to