The subject terms being used for our research guides are the result of a fairly intensive debate by a joint team from the Research Guides Management Team and the Drupal Discovery Content Team. The list is intended to serve as both a taxonomy for guides and the top level of a multi-level taxonomy for databases. A lot was borrowed from the original LibGuides subject system guidelines. The goal was to create a short list of top-level subjects that are easy to browse. It's important to emphasize that these are browsable subjects that are supplemented by a full-text search box.
That said, the LibGuides subject list is constantly evolving. Many people have made suggestions along the way, and most of them have resulted in improvements. So please, send your concerns and suggestions for alternate terms or different groupings. We've actually left one slot empty for the subject we didn't think of. However, in general if you want to add a subject be prepared to nominate another for deletion. It's not enough to argue that your subject is important enough to have its own entry. It's got to be more important than something already on the list which can be bumped or merged.
The LibGuides system automatically lists guides in each subject aphabetically, but this often puts the major guides low on the list. Unfortunately, unlike LibGuides 1, we have no way to re-order guides within a subject right now. This is at the top of our wish list to Springshare!
In addition to categorizing guides by Subject, LibGuides v2 also groups them by Type. The system came with six default types (listed below), which we can re-name but not add to. Though the guide type does not display to the user, it controls a lot of behind-the-scenes functionality, so it's important to choose the right one! Specifically...
Do not use tags to provide alternative search terms! That function is now handled by Metadata fields.
Tags serve two complementary purposes.
In general, tags should define groups of guides. Also remember that most of the time people won't see the tags until they're already looking at the guide, so important descriptive terms that define the scope of your guide belong in the Description, not the tags.
Tags should be a minimum of three characters and use normal capitalization. (Reminder: academic disciplines are not proper nouns.)
The following tags have been standardized and are in use by other discovery tools for grouping guides. Links indicate where the tag is being used to power a widget or search. Please use these tags only for their listed purpose.
* LSC guides are by definition about primary sources, but already have their own group. So if you want a list of all primary source guides, use both the LSC group and the primary source tag.
or
Metadata fields are html tags recognized by search engines, including both LibGuides' built-in search engine and third-party engines like Google and Yahoo. LibGuides automatically fills in a bunch of Dublin Core metadata fields for you, but you can add your own to provide alternative search terms. Just remember, there's no need to duplicate words or phrases already in the DC fields, which include: