Difference between revisions of "TagTeam versions"

From Harvard Open Access Project
Jump to: navigation, search
(Version 2.1.0.6)
(Version 2.1.0.6)
Line 22: Line 22:
 
* Email notifications to taggers now include changes made by hub-wide filters, not just changes made by human taggers.  
 
* Email notifications to taggers now include changes made by hub-wide filters, not just changes made by human taggers.  
  
* When users add a tag to a record that already had that tag, the original tagger will not receive an email notification.
+
* When users add a tag to a record that already had that tag, the original tagger will not receive an email notification about the addition. (And of course, TagTeam will only record one instance of the tag.)
  
 
* When viewing tag libraries, users were formerly limited to viewing 25 items per page. They may now choose to see 25, 50, and 100 items per page.  
 
* When viewing tag libraries, users were formerly limited to viewing 25 items per page. They may now choose to see 25, 50, and 100 items per page.  
  
* Hub owners may now make any character a tag delimiter (such as the space). They may have more than one tag delimiter (like both the comma and the space). The comma remains the default tag delimiter, and cannot be removed from the set of tag delimiters.  
+
* Hub owners may now make any character (such as the space) a tag delimiter. They may have more than one tag delimiter (like both the comma and the space). The comma remains the default tag delimiter, and cannot be removed from the set of tag delimiters.  
  
 
* Hub owners may now unsubscribe from input feeds.
 
* Hub owners may now unsubscribe from input feeds.
Line 33: Line 33:
 
* TagTeam now strips unnecessary parameters from item URLs, maximizing that odds that items with the same basic URL will be recognized as duplicates. This will maximize the power of TagTeam's dedupe algorithm, and minimize the odds that users will re-tag items already tagged.
 
* TagTeam now strips unnecessary parameters from item URLs, maximizing that odds that items with the same basic URL will be recognized as duplicates. This will maximize the power of TagTeam's dedupe algorithm, and minimize the odds that users will re-tag items already tagged.
  
* In hubs with standard prefixes (the way OATP uses "oa." as a standard prefix), TagTeam will now automatically correct "prefix+comma" with "prefix+period".  
+
* In hubs with standard prefixes (the way [[Open Access Tracking Project | OATP]] uses "oa." as a standard prefix), TagTeam will now automatically correct ''prefix+comma'' with ''prefix+period''.  
  
 
* In all lists of items, users can sort by date tagged or date published, and in ascending or descending order. The default for each list is to sort by date tagged in descending order (most recent first). This applies to the master list of items tagged in a hub, the list of items with a given tag, the list of items returned by a search, and the list of items tagged by a given tagger. In addition, tag records now show both date tagged (old) and date published (new).  
 
* In all lists of items, users can sort by date tagged or date published, and in ascending or descending order. The default for each list is to sort by date tagged in descending order (most recent first). This applies to the master list of items tagged in a hub, the list of items with a given tag, the list of items returned by a search, and the list of items tagged by a given tagger. In addition, tag records now show both date tagged (old) and date published (new).  

Revision as of 12:54, 22 August 2018

This list starts with version 2.1.0.2. One day we may go back and add details on earlier versions. It focuses on major new features. It omits minor features, and only includes bug fixes when they are notable.

Version 2.1.0.6

(August 20, 2018)

  • The "Bookmarks" tab is now called the "Taggers" tab.
  • In the Taggers tab, the list of taggers can be sorted by username, date started, most recent tagging, and number of items tagged.
  • Users may now use tagger usernames (along with tags and keywords) in boolean searches.
  • Email notifications to taggers now include changes made by hub-wide filters, not just changes made by human taggers.
  • When users add a tag to a record that already had that tag, the original tagger will not receive an email notification about the addition. (And of course, TagTeam will only record one instance of the tag.)
  • When viewing tag libraries, users were formerly limited to viewing 25 items per page. They may now choose to see 25, 50, and 100 items per page.
  • Hub owners may now make any character (such as the space) a tag delimiter. They may have more than one tag delimiter (like both the comma and the space). The comma remains the default tag delimiter, and cannot be removed from the set of tag delimiters.
  • Hub owners may now unsubscribe from input feeds.
  • TagTeam now strips unnecessary parameters from item URLs, maximizing that odds that items with the same basic URL will be recognized as duplicates. This will maximize the power of TagTeam's dedupe algorithm, and minimize the odds that users will re-tag items already tagged.
  • In hubs with standard prefixes (the way OATP uses "oa." as a standard prefix), TagTeam will now automatically correct prefix+comma with prefix+period.
  • In all lists of items, users can sort by date tagged or date published, and in ascending or descending order. The default for each list is to sort by date tagged in descending order (most recent first). This applies to the master list of items tagged in a hub, the list of items with a given tag, the list of items returned by a search, and the list of items tagged by a given tagger. In addition, tag records now show both date tagged (old) and date published (new).
  • TagTeam now supports hub-wide supplement tag filters, above and beyond the pre-existing set of "add", "modify", and "delete" tag filters. Supplement filters let hubs supplement a given tag (for example, "mexico") with another tag ("latin_america") throughout the hub, prospectively and retroactively.
  • When taggers tag an item by mistake, they may now remove it from the hub. Hub owners may also remove any item in the hub.
  • When hub owners try delete a whole hub, they receive "are you sure?" query first.
  • There is now a statistics tab giving an overview of activity on the hub. It's visible even to non-members of the hub.
  • Users may now edit the title, description, and URL of item records.
  • Users may copy or move items from one hub to another, when they have tagging rights in both hubs.
  • In the Taggers tab, users could always hide or display the data on an individual tagger (showing when they last tagged and how many items they've tagged). They may now toggle hide/display for the entire list.
  • When users click on a tag, there was always a pop-up menu now offers options, and the options offered were context sensitive. Now the menu offers more options in more contexts.
  • There are now more options in the Settings tab for hub owners. Among them: to change the tag delimiters; to change the tag prefix (if any); to list hub-approved tags and decide whether to limit tag suggestions to those approved tags; to remind taggers to add a description when they leave the description field empty; to create a publicly visible "scoreboard" of the most productive taggers and most common tags; and to make it optional or non-optional for taggers to receive email notifications when their items are modified by later taggers.
  • Several operations that were slow are now faster, for example, displaying the list of tag suggestions, displaying the effects of filters, and changing the sort order on a list.

Version 2.1.0.5

(May 18, 2018)

  • The master list of Users now supports sorting on usernames and other user properties.
  • In lists of tagged items, the green "+" icon (to add new tags) appears next to all items, not just some.
  • The email notification option moved from the "Team" tab to the "Settings" tab.
  • Hub owners have a new setting to prevent taggers from opting out of email notifications when hub members update their tag records.
  • Hub owners may now choose any other character (such as a space) to be a tag delimiter, along with the comma.
  • Hub owners may now designate "approved tags" and limit the tag-suggestion list to approved tags.
  • Hub owners now have a Messaging tab for sending email messages to all or some members of the hub.
  • There is a new Statistics tab visible to authorized hub members.
  • Administrators now have a more useful and intuitive interface.

Version 2.1.0.4

(October 20, 2017)

  • We clarified the text on the email notification sent to taggers when their tag records have been changed.
  • TagTeam now displays subscriber counts for its RSS, Atom, and JSON tag feeds.
  • The "About" page now links to the TagTeam home page.
  • The "Tags" tab now displays summary statistics at the top of the page.
  • What used to be called the "Community" tab is now called the "Team" tab.
  • Authorized users may now change and delete tags from the bookmarklet, without entering the rest of the program. (They could always add tags from the bookmarklet.)
  • Hub owners may now choose to use the space as a tag delimiter, rather than the default comma.

Version 2.1.0.3

(February 28, 2017)

  • Authorized users may not revise or update URLs in tag records.
  • More views or displays now give authorized taggers the option to modify or delete existing tags.
  • TagTeam can now create a feed of all the items tagged by a given user, and a feed of all the items in which a given user applied a given tag.
  • The Bookmarks tab gives better information on the listed members of the hub.
  • TagTeam no longer lets undated or misdated items hog the top spot in a list of items sorted by date of tagging.
  • TagTeam now records the date an item was published, not just the date it was tagged.

Version 2.1.0.2

(February 21, 2017)

  • The "Community" tab now displays the number of users authorized to tag for the hub.
  • TagTeam automatically approves new users with email addresses from .edu domains. Others are asked to describe the academic or research project they have in mind.
  • Taggers got the option to receive email notifications when other taggers updated or modified their tag records.
  • Hub owners now have a more intuitive interface for granting privileges to new members of their hub.
  • Account creation is now conditional on approving Terms of Service.