bansp
commented
7 years ago As for tags, we could go for, e.g., "SSK:XML" (i.e. using "SSK" as the namespace that SSK harvests). But it struck me that a LOT of resources would get tagged by that (roughly the same number that would get tagged by bare "XML" ;-) ), and we want the list presented to the user in the SSK, in the format conversion scenario, to be finite...
Would it make any sense to go for "SSK:sc_formatConversion", i.e., to use the scenario name? In that case, the list of resources corresponding to the parameter value "XML", would be produced by searching Zotero for the tag "XML" in conjunction with the tag "SSK:sc_formatConversion". This of course requires the scenario makers to also pay attention to the internals of Zotero (instead of relying on crowd-sourced wisdom). But in this very case, maybe the aim of the SSK is worth the extra time spent on tagging selected Zotero resources with "SSK:sc_formatConversion" (?)
Please formulate some conventions for creating collections in Zotero, adding tags, etc.
One issue are the tools: If we refer to tools should I put a link to a tool in a specific collection or should I tag it with e.g. "tool" Another issue are resources that do not fit in the current collection model, e.g. a generic resource that can not be connected with one specific standard (or the way around: it can be connected with a lot of standards, e.g. identify the file/data format by looking at the file extension in the list of wikipedia: https://en.wikipedia.org/wiki/Filename_extension - the list to be the resource)
Sum up: When to create collections, when to use tags? Naming conventions for collections and tags?