Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
| collections_and_tags [2017/07/11 05:18] – [Collections] sean | collections_and_tags [2017/07/30 15:11] – [Collections and Tags] typo pjweiss |
|---|
| "Collections" allow hierarchical organization of groups of items, in advance of adding items to your library. Item may be placed in multiple locations (sub-collections) in your library collection. Items may then be retrieved by "drilling down" into the hierarchy. | "Collections" allow hierarchical organization of groups of items, in advance of adding items to your library. Item may be placed in multiple locations (sub-collections) in your library collection. Items may then be retrieved by "drilling down" into the hierarchy. |
| |
| "Tags" (also called "keywords" in other contexts) allow for detailed characterization of an item, and have the unique advantage of allowing the formation of ad-hoc collections //after// adding items to your library (e.g., one can use tags to locate items tagged "Sumarian" + "history", and so on.) | "Tags" (also called "keywords" in other contexts) allow for detailed characterization of an item, and have the unique advantage of allowing the formation of ad-hoc collections //after// adding items to your library (e.g., one can use tags to locate items tagged "Sumerian" + "history", and so on.) |
| |
| Tags are portable, but collections are not: copying individual items between Zotero libraries will transfer their tags, but not their collection placements. Both organizational schemas have unique advantages. Experiment with both to see what works best for your own workflow. | Tags are portable, but collections are not: copying individual items between Zotero libraries will transfer their tags, but not their collection placements. Both organizational schemas have unique advantages. Experiment with both to see what works best for your own workflow. |
Upgrade Storage