| thiemowmde added a comment. |
Quickly talked to @daniel:
- What Cirrus stores internally should be in different fields. There is no disagreement on that.
- What I'm talking about above is that we do not have to expose these fields individually to the user. The backend code can understand that, for example, filemime:application/vnd.geo+json is about a MIME type that is known to be in the Data: namespace, and magically use the proper Cirrus field, even if it is not called filemime internally.
- I suggest the following algorithm for a unified filetype:… keyword that accepts everything. The order is "most specific" to "least specific". filemime:… can be an alias for filetype:… with this algorithm.
- Compare the users input with a list of known MIME types in the relevant namespaces (only Data: and File: for a start). Either use filemime or filedata (or however this new field is called) internally, depending on the namespace.
- Compare the users input with a list of known content types. Use the internal Cirrus field for the content type.
- Compare the users input with a list of known file types (like "audio" and "video"). Use filetype internally.
- A minor edge case is that pages in the File: namespaces do have two MIME types, one for the file, and one for the file description page. We must make sure File: pages are not indexed by their application/x-wiki MIME type.
TASK DETAIL
EMAIL PREFERENCES
To: Yurik, thiemowmde
Cc: daniel, aude, Lydia_Pintscher, thiemowmde, Jonas, Aklapper, debt, Pokefan95, D3r1ck01, Izno, Wikidata-bugs, Base, El_Grafo, jayvdb, zhuyifei1999, Yurik, Steinsplitter, Mbch331, Jay8g
Cc: daniel, aude, Lydia_Pintscher, thiemowmde, Jonas, Aklapper, debt, Pokefan95, D3r1ck01, Izno, Wikidata-bugs, Base, El_Grafo, jayvdb, zhuyifei1999, Yurik, Steinsplitter, Mbch331, Jay8g
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
