Difference between revisions of "TagTeam versions"

From Harvard Open Access Project
Jump to: navigation, search
(Version 2.2.0.4)
Line 17: Line 17:
 
* We fixed a bug that sometimes caused mislabeled feed items to block feed updates.
 
* We fixed a bug that sometimes caused mislabeled feed items to block feed updates.
  
* Every attempt to create a hub-wide filter now triggers a verification dialog box.
+
* Every attempt to create a hub-wide filter now triggers a verification ("Are you sure?") dialog box.
  
 
== Version 2.2.0.1 ==
 
== Version 2.2.0.1 ==

Revision as of 13:01, 3 February 2020

Most recent versions at the top.

This list only goes back to 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.2.0.4

(February 3, 2020)

  • We fixed a bug that sometimes caused a supplement filter to add the supplementary tag to unrelated records.
  • We fixed a bug that sometimes caused mislabeled feed items to block feed updates.
  • Every attempt to create a hub-wide filter now triggers a verification ("Are you sure?") dialog box.

Version 2.2.0.1

(July 18, 2019)

  • The "About" page now lists TagTeam's supporting funders.
  • The "Filters" tab shows basic stats at the top.
  • In the bookmarklet form, the "Add to TagTeam" button is now at the top, not the bottom. Taggers can click it without scrolling.
  • In editable text boxes, users may hit the "enter" key instead of clicking the "Submit" button.
  • Logging out no longer triggers error messages.
  • TagTeam responds more gracefully when it receives bounce messages after sending emails to invalid user addresses.
  • The command to delete an item now works and take effect quickly, as opposed to not working or taking effect only after a long delay.
  • RSS and Atom feeds invalid under the W3C validator are now valid.
  • A new captcha should reduce spam sent to hub owners through the "Contact" tab.
  • Screen views that should show scrollbars on Firefox now show scrollbars.
  • When users tag an item already tagged, the bookmarklet not only shows the tags already applied (as in the past), but also the usernames of the taggers who applied them.
  • When users try a URL for a tag with no instances, a new error message explains that that hub has no instances of that tag.
  • When users change their usernames, the changes show up everywhere they should.
  • When users use the "Contact" form to request certain rights in a hub, the rights language in the form matches the rights language in the hub's "Team" tab.
  • When users tag an item with optional URL parameters, TagTeam (usually) removes the parameters before comparing the URL with other items tagged in the same hub. Hence, deduplicating items in the hub and all hub feeds is more effective. This feature also frees up tagger time spent tagging items already tagged and/or removing optional URL parameters manually. There's no universal pattern for these parameters, and TagTeam doesn't yet recognize all the different ones. But it recognizes many will do better over time.
  • When a filter modifies a given tag, items with the original tag (and not the new tag) no longer show up in searches. When those filters are deleted, items with the original tag return again.
  • When a filter changes a deprecated tag to an approved tag, users searching for the deprecated tag will see a friendly suggestion to search for the approved tag. This also works for boolean searches containing one or more deprecated tags.
  • Users can exercise more of their rights directly in the bookmarklet form, without entering TagTeam itself.
  • Users can now search for items by date or date range. These searches can apply to the date published or the date tagged, at the user's choice.
  • Users cannot create circular modification filters (changing tag A to B, and vice versa). When they try, they receive an error message.
  • When users try to create a filter adding a certain tag to every item in the hub, they encounter an "Are you sure?" confirmation box.
  • Users may create more than one supplement filter for the same tag, for example supplementing A with B, but also supplementing A with C.
  • Users may create filters with wildcards, for example changing foo* to foobar, where * represents any string of characters.
  • Users can add an item-level "delete" filter even when there is already an item-level "add" filter for the same tag.
  • Users with tagging rights in two hubs may copy or move an item from one hub to another.
  • Users may now remove themselves from a hub. Formerly only the hub owner could remove them. When users are removed, the items they tagged remain in the hub, but the users receive no further feedback when those tag records are updated.
  • Only hub owners can now change hub-wide settings.
  • Hub owners now have editable field associated with each tag write out their tag definitions, descriptions, or recommendations. When filters deprecate tags, hub owners have an option to attach the old definition to the new tag.
  • Hub owners may now prune the bookmarklet list of suggested tags. They may classify any tag in the hub as one to appear or not appear in the list. They may also turn on an option removing all deprecated tags from the list, when a deprecated tag is one modified by a "modify" filter.
  • Hub owners may now completely remove items from a hub, for example, spam or off-topic items.
  • Other small additions and bug fixes.

Version 2.1.0.6

(August 20, 2018) (Also see the announcement of this version, August 28, 2018.)

  • There is now a Statistics tab giving an overview of activity on the hub. It's visible even to non-members of the hub.
  • 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.
  • In the Taggers tab, users could always hide or display data on individual taggers (showing when they last tagged and how many items they've tagged). They may now toggle hide/display for the entire list.
  • Users may now edit the title, description, and URL of item records, not just the tags.
  • When users click on a tag, there was always a pop-up menu offering options, and the options were context-sensitive. Now the menu offers more options in more contexts.
  • Users may now use tagger usernames (along with tags and keywords) in boolean searches.
  • 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.
  • Email notifications to taggers now include changes made by hub-wide filters, not just changes made by human taggers.
  • Email notifications to taggers now take hub-wide filters into account. If you tag an item, and a subsequent tagger adds TagA, and a hub-wide filter converts TagA to TagB, then your email notification will tell you that someone added TagB (not TagA) to that item.
  • 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.)
  • 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. The new filters supplement a given tag (for example, mexico) with another tag (latin_america) throughout the hub, prospectively and retroactively.
  • 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 using a standard tag prefixes (the way OATP uses "oa." as a standard tag prefix), TagTeam will now automatically correct prefix+comma with prefix+period.
  • 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 will receive an "Are you sure?" query first.
  • Hub owners may now make any character (such as the space) a tag delimiter. They may have more than one tag delimiter (for example, both the comma and the space). The comma remains the default tag delimiter, and cannot be removed from the set of tag delimiters.
  • Users who create a hub subscription to an input feed from an external source may now unsubscribe the hub from those feeds. Hub owners may also unsubscribe the hub from any input feeds.
  • 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.