Development

You are currently browsing the archive for the Development category.

The trick of tagging

One concept we’re wrestling with during the early development of the Prior Art Database is how best to help users find and label information. Tagging individual entries is useful to a degree, but tags (for good reason) are very general labels. Patent researchers, attorneys, innovators, and the general public are all going to want to search for very specific information.

Tags will be useful to describe generally what an innovation is. But we’ll need a more specific method for labeling and searching for what the innovation does. A way for users to define the constituent parts of a technology in a very focused search.

What’s the best way to do this? There is no universally accepted taxonomy that organizes software, often because the functionality of an individual piece of software crosses categories. It may be helpful to have a classification system that is separate from tagging. When you search a library catalog, you can search by title, subject, author, or a keyword that appears in the text. Tags, perhaps, could function as a “subject” search, with the individual functions of innovations being identified as keywords.

An example: Let’s say a user is creating an entry to describe a program that generates random environments graphics within a video game. Tags for such an entry could consist of “randomization,” “graphics,” or “games.” These general categories would be useful to someone browsing for what’s generally out there in this area. But it will also be important for a user to come to our database and identify specific constituent parts of technology such as “polygon triangulation algorithm,” or something even more specific such as “Chazelle’s algorithm” or “Seidel’s algorithm.”

Essentially, we want to differentiate between function, which will be described by tags, and constituent parts, which will need its own system. We already have in tagging a useful tool to identify broadly what a technology is, such as “transportation.” What we could use some help with is a system of cataloging the specifics, such as “spark plug, tire, and fuel injector.” Your thoughts and comments are very welcome.

On Our Way

We are getting very close to having a functional interface for the Prior Art Database. Features in development this week include discussion threads for each reference. This will be an important tool for helping us understand how to better organize information for users, as well as provide an opportunity for contributors to critique the quality or content of an entry. We’re hoping that these spaces can be a way for users to engage one another — perhaps even find others who are interested in the same kinds of information or innovations — and help to build up a community.

Also in the works are improvemets to the visual layout, and experimentation with autocompletion styles. Since many, many users will be contributing information and tagging entries, it’s important to have a tool that suggests tags to keep the tag cloud from dissolving into a million different words for the same idea. This tool will be especially important as we can already see that some creative ideas will be needed in our search for the best way to help users clump useful entries with tags as well as pinpoint very specific entries in the database.

It’s still too soon to begin discussion of beta testing and the volunteers we’ll need for that, but it is very exciting to see that we are on our way.