Top contributors to this page: DerekPeaceTech
To find an image, do a Google image search of the tool. Find an image about 600px wide, if possible. Copy the image URL and paste into the box below.
What is the name of the tool?
| Tool Class
To what "family" does the tool belong? Pick as many categories as are appropriate. EG: Data Collection, Security, etc. The wiki will automatically create a link to the relevant tool class.
|Transcript, Transparency Tools, Data Analysis|
Who made the tool? Sometimes the tool name and the developer name are the same, and sometimes, they are different.
| Date Created
What was the date when the tool was first launched?
| Still Maintained?
Do the developers of the tool continue to work on it, adding features and fixing problems?
| Open Source?
Is the tool's source code original source code freely available and may it be redistributed and modified? (This makes it possible for users to employ the tool for free, with some technical effort.)
Pick the platforms on which the user would primarily use the tool. Be as selective as possible. If a tool works mainly in the browser, select "Web". If the user can technically load the interface on a smartphone but have a very poor experience, do not select "Android" or "iOS". "Mac" and "PC" are for apps that must be installed to a machine in order to run, as opposed to running from a browser.
What is the main website where a user can learn more about the tool? (Remember to include "http://)."
| Payment Structure
How, if at all, does a user pay to use the tool. Select all that apply: "Free" if there are components of a service that can be used for free; "Paid" if payment is required (either one-time, or at a given rate upon use) for use of the tool's full functionality; "subscription" if a monthly payment is required.
| Languages Supported
What languages does the app's interface support? Note: some apps allow users to communicate in other languages but require the user to use an English language interface. In this case, the app is considered only to support "English".
| Skill Level Needed
An Open Source tool for making transcripts easy to read, search and share on the modern internet. Often when meetings and discussions are recorded, the output is in form of a large text file or, a PDF that one is unable to parse. SayIt breaks these transcripts down into easily readable, searchable, linkable conversations.
Meetings are at the heart of institutional decision-making, and transcripts of meetings provide us with a window into the decision-making process. SayIt is a tool for recording and analyzing transcripts of parliamentary proceedings, court hearings and other records of events.
From the SayIt Website:
"Transcripts are a kind of oil that greases the wheels of well-functioning societies. They let people discover when powerful people have made pronouncements that affect less powerful people. We believe that by making transcripts function better, more people will end up learning about decisions and opinions that affect their lives."
SayIt can be used by:
- Journalists, who want to store, search and publish both the transcripts of specific events, and databases of speeches and statements by politicians.
- Officials in courts, who want to produce transcripts that are quicker and easier to use.
- Officials in parliaments and other assemblies, who want to make transcripts that the public and politicians can more easily make use of.
- Researchers who have records of interviews with subjects, who want that data to be quick and easy to access, even if private.
- Campaigners and activists who want to track what certain people say about key issues.
SayIt helps achieve transparency by making it easier for viewers to discover what leaders are saying and to attribute their words back to them.
SayIt can support conversations of any language. The designers have said they are interested in supporting the translation of the website into non-English languages.