npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

turk

v0.7.0

Published

Amazon Mechanical Turk API - more coverage, less ORM

Downloads

27

Readme

turk: Amazon Mechanical Turk API

npm version

See http://en.wikipedia.org/wiki/Web_Services_Description_Language In combination with http://docs.aws.amazon.com/AWSMechTurk/latest/AWSMturkAPI/ApiReference_WsdlLocationArticle.html

Install:

npm install turk

Or merge the following into your package.json:

{
  "dependencies": {
    "turk": "*"
  }
}

SQS Message Payload

The body of each SQS message is a JSON-encoded structure that provides support for multiple events in each message.

The following specifications are taken from the AWS MechTurk documentation.

The JSON-encoded structure consists of the following properties:

  • EventDocVersion: This is the requested version that is passed in the call to SetHITTypeNotification, such as '2006-05-05'. For a requested version, Mechanical Turk will not change the structure or definition of the output payload structure in a way that is not backward-compatible.
  • EventDocId: A unique identifier for the Mechanical Turk. In rare cases, you may receive two different SQS messages for the same event, which can be detected by tracking the EventDocId values you have already seen.
  • CustomerId: Your customerId.
  • Events: A list of Event structures, described below.

The Event structure consists of the following properties:

  • EventType: A value corresponding to the EventType value in the notification specification data structure.
  • EventTimestamp: A dateTime in the Coordinated Universal Time time zone, such as 2005-01-31T23:59:59Z.
  • HITTypeId: The HIT type ID for the event.
  • HITId: The HIT ID for the event.
  • AssignmentId: The assignment ID for the event, if applicable.

License

Copyright 2013–2015 Christopher Brown. MIT Licensed.