Peter Suber has made a call for people in the OA community to tag items on Connotea as a part of the Open Access Tracking Project. The aim of the project is to get people to converge on using a common tag for tracking open access news. The proposed tag is oa.new.
Great! I’m a fan of open data, open source and open knowledge and I’m thrilled that people can find Connotea useful in organising their information. He raises a number of points around using Connotea for this, and just wanted to quickly comment on some of them.
- Connotea feeds only deliver the 10 most recently tagged items, and the project is already tagging more than 10 items per day. Hence, use a feed reader which refreshes several times a day and stores past items until you’ve read or deleted them. Bloglines stores the most recent 200 items, and Google Reader appears to store all past items until you’re ready to delete them. There may be many other readers with this feature as well; I just haven’t had time to check. Note that for now the email feed is stuck with the 10 item limitation.
By default we deliver the 10 most recent RSS items, however you can call a larger number by specifying the amount in the url like so: feed://www.connotea.org/rss/user/IanMulvany?num=100. I believe that in principle there is a limit of 1000 items that can be retrieved, but we would appreciate it if you restrict calls to a reasonable number.
One thing I’d like to call out. The links in our RSS feeds link to the bookmarked resources, and not to the Connotea page. We used to link to the Connotea page, but that didn’t seem right, so we changes this last year.
Something that is not well know, but might be of interest, the parsing engine can also display a library page in plain text using the following uri structure:
http://www.connotea.org/txt/user/IanMulvany
This can be handy if you want to quickly get data into a text document.
- If two or more users tag the same item with the same tag (like oa.new), then the item will appear in the feed two or more times. This doesn’t prevent the feed from becoming comprehensive, but it makes an already-large feed larger than necessary. I welcome suggestions and work-arounds, including other tagging services that don’t create this problem.
I’m not sure I see the problem here. The RSS feeds provide a time ordered list of when items were tagged, the the newest items on top. Over time one would expect the same item to appear in a feed if it gets tagged again by a new person.
If you go to the item page in Connotea this is a different matter. We do display one instance per person who bookmarked an item. There are two reasons for this. The first is that you see which tags different use has used for the same resource. The second reason is just one of code efficiency, it was just easier to reuse the template for a single bookmark in this way. It may indeed not be optimal, and if people are having a really hard time with this I’m willing to consider a change.
- Connotea users already use at least four different tags for OA-related sites: open access, open_access, open-access, and openaccess. The variant forms make it hard for users to find all the relevant feeds; they also prevent any single feed from taking full advantage of the collective tagging effort. More to the point for this project, they are not limited to new developments and are often used to tag older developments. Fortunately, OATP is fully compatible with existing tags. I’m not asking anyone to stop using existing tags, but merely to start using oa.new for developments that are new within the last six months.
If Connotea users would like to automatically add the oa.new tag to items that they have already tagged with some other related tag then they can do this with the “Rename tag” feature. It’s a bit more powerful that just renaming. You can also use it to split a tag into multiple new tags. I’ve just renamed my “openaccess” tag to “openaccess” and “oa.new”, effectively rolling in the new tag to my previously tagged items, without losing the tag I had been using. We have discussed tag relations, and that is something I would like to introduce at some point in the future, but other commitments mean that we are unable to introduce this feature right now.