|
|
| (5 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| [[File:oad2.jpeg|60px]] This list is part of the [http://oad.simmons.edu Open Access Directory].
| | This page [http://cyber.law.harvard.edu/hoap/OATP_tips moved] on May 24, 2015. Please update your bookmarks. |
| | |
| {| align="right"
| |
| | __TOC__
| |
| |}
| |
| | |
| <!-- <center>
| |
| {| class="wikitable" style="text-align:center" border="0" cellpadding="8" cellspacing="0"
| |
| | style="background:lightgray; color:black" | This page has '''not''' yet been updated to reflect the transition from Connotea to TagTeam. it will be soon
| |
| |}
| |
| </center>
| |
| -->
| |
| * This is a section within the larger [[OA tracking project]] (OATP).
| |
| | |
| * Project ''tips'' are suggestions on how to help or be helped by the project. For more settled decisions and agreements on how to carry out the project, see the page on project [[OATP conventions | conventions]].
| |
| | |
| [[Category:Research about OA]] [[Category:Working for OA]]
| |
| | |
| == Tips for readers ==
| |
| | |
| * '''Reading full text'''
| |
| ** An OATP feed consists of tag records, which contain brief summaries or descriptions, with links to full texts. They do not contains full texts themselves. For some purposes, this austerity is an advantage: OATP tag records are easier to read or skim than an equal number of full texts. But for other purposes, it's a disadvantage: they contain less information than full texts.
| |
| ** If you want to skip the austere tag records and jump straight to the tagged texts themselves, then subscribe to the project feed with Google Reader. Put the "Next" bookmarklet in your browser toolbar. Clicking on it will take you to the next item in the feed --not the next austere tag record but the full-text item tagged by the next tag record.
| |
| *** Clearly this recommendation has been obsolete since Google pulled the plug on Reader in July 2014. If you know other tools with the same feature described here, please let us know.
| |
| | |
| * '''Searching'''
| |
| ** You can search the whole corpus of OATP tag records inside [http://tagteam.harvard.edu/ TagTeam]. You needn't be a registered TagTeam user to do so.
| |
| *** For details on the flexibility of the TagTEam search engine, see the [http://cyber.law.harvard.edu/hoap/TagTeam_basics#Searching section on searching] in the [http://cyber.law.harvard.edu/hoap/TagTeam_basics TagTeam manual].
| |
| ** If you subscribe to an OATP feed with Google Reader, then you can take advantage of its Google-based searching of the feed all the way back to the feed's beginning, even if you didn't start subscribing until some later date.
| |
| *** Again, this powerful Google Reader feature is no longer available, and we welcome suggestions for other tools with the same feature.
| |
| | |
| == Tips for taggers ==
| |
| | |
| | |
| | |
| | |
| | |
| * '''Tagging events'''
| |
| ** If you tag a conference or workshop, before or after it occurs, take a moment to see whether it's listed on the OAD [[Events]] page. If not, please add it.
| |
| ** People looking for events in their area (to see what they could attend), or at a given future time (to avoid conflicts for their own future events), consult the OAD Events list more often than the any OA-related feed. Hence, if you had to choose, it's more helpful to post upcoming events to the OAD list than to tag them for OATP. But unless you're very short on time, you don't have to choose and can do both.
| |
| | |
| * '''Tagging items that may soon disappear'''
| |
| ** If you tag an item that may not stay online long, such as a job ad, try to put all the relevant details in the description field for preservation.
| |
| | |
| * '''Neutral tagging'''
| |
| ** Tagging an item for OATP is not an endorsement. If a new article is relevant to OA, but you strongly disagree with hit, OATP still wants to include it. OATP provides alerts and organizes knowledge of the field. It leaves critique for articles, blog posts, forum discussions, conference presentations, and other venues.
| |
| ** The "description" box in the tagging dialog should also be a neutral excerpt or paraphrase. Don't use it to express opinions about the work you are tagging.
| |
| *** If you're moved to write a rebuttal to a work you tag for OATP, don't do it in the OATP tag record. Write your rebuttal in a separate blog post (or other online location) and then tag your rebuttal.
| |
| ** The ''oa.negative'' tag is for objections, obstacles, or setbacks to OA, not for low-quality work about OA.
| |
| <!-- ** Some tagging platforms offer a "comment" box in addition to a "description" box. If your platform does so, then your "description" should be neutral, but your "comment" can be highly opinionated. -->
| |
| | |
| * '''Identifying spam'''
| |
| ** If you see an item utterly unrelated to OA in a project feed, then take a moment to tag it with ''oa.spam''.
| |
| ** The [http://tagteam.harvard.edu/remix/oatp primary project feed] for OATP omits items tagged with ''oa.spam''. If you notice some spam in the feed, it's already too late for your tag to exclude the spam from the feed. But your tag will still help project managers identify spam (to exclude it from searches) and expel spammers.
| |
| <!-- ** Also see the [http://oad.simmons.edu/oadwiki/Talk:OA_tracking_project discussion] of this strategy for dealing with spam. -->
| |
| | |
| * '''Identifying countries and languages'''
| |
| ** Tag countries and languages separately, e.g. ''oa.argentina'' and ''oa.spanish'', even if they're very similar, e.g. ''oa.spain'' and ''oa.spanish''.
| |
| | |
| == Tips for others ==
| |
| | |
| * '''If you have a blog''':
| |
| ** Put a [http://oad.simmons.edu/oadwiki/OATP_mashups#Widgets_to_display_the_feed widget] in the sidebar to display the most recent items from the project feed.
| |
| | |
| * '''If you maintain a web page that links to an OATP tag library''':
| |
| ** Make sure that the entry for that tag on the [[OATP tags| tags page]] mentions your link to the tag library. This not only gives you more exposure, but shows how people are using the OATP links.
| |
| ** Check the [[OATP tags]] page periodically to see whether the tag has been deprecated and replaced with another. If it has, then you should link to the library for the new and preferred tag.
| |
| <!-- ** Some OATP tags are not about to change, such as [http://www.connotea.org/tag/oa.new oa.new] and [http://www.connotea.org/tag/oa.france oa.france]. But others are in flux and may change. For example, since its launch OATP has shifted from singular to plural nouns, deprecating ''oa.repository'' in favor of ''oa.repositories'', and has shifted in the way it treated phrases with spaces, deprecating ''oa.saudiarabia'' in favor of ''oa.saudi_arabia''. -->
| |
| | |
| * '''If you want to link to OATP output''':
| |
| ** To link to the primary project feed (HTML edition): <code><nowiki>http://tagteam.harvard.edu/remix/oatp</nowiki></code> .
| |
| ** To link to the tag library for a given ''tag'': <code><nowiki>http://tagteam.harvard.edu/hubs/3/tag/TAG</nowiki></code> . For example: <code><nowiki>http://tagteam.harvard.edu/hubs/3/tag/oa.policies</nowiki></code> .
| |
| <!-- restore these when TagTeam supports these kinds of links
| |
| ** To link to the tag library of a given ''tagger'': <code><nowiki>http://www.connotea.org/user/TAGGER</nowiki></code> . For example: <code><nowiki>http://www.connotea.org/user/petersuber</nowiki></code> .
| |
| ** To link to the tag library of a given ''tagger'' for a given ''tag'': <code><nowiki>http://www.connotea.org/user/TAGGER/tag/TAG</nowiki></code> . For example: <code><nowiki>http://www.connotea.org/user/petersuber/tag/oa.new</nowiki></code> . -->
| |
| <!-- ** To link to an individual ''tag record'': First go to the ''oa.new'' tag library, [http://www.connotea.org/tag/oa.new oa.new] (or any other relevant tag library). Scroll or search until you find the tag record to which you want to link. The URL you want is under the word "info". For example: <code><nowiki>http://www.connotea.org/article/fe5f4475e5b415ecd81a9732da2b854a</nowiki></code> . -->
| |