Toolbox for metadata managment

From wiki.gpii
Jump to: navigation, search

A 202.4 - Toolbox for professional and vendor entry and maintenance of Metadata: functional description.

The Toolbox for entry and maintenance of Metadata (TEMM) will be an add-on to the Semantic Alignment Tool (SAT). The reason for that is to avoid having separate tools that have similar objectives and operate on the same set of data (i.e. the metadata/ontology and registry of common terms).

The toolbox will be used by manufacturers, vendors (or database administrators) to:

  • enter data about their products, including:
    • Basic product information (name, typology, text description, manufacturer, …)
    • Technical details according to the metadata vocabulary (currently based on the EASTIN taxonomy).
    • Specific settings and their matching with common term registry

<those functions are basically already in place in the current SAT>

  • Propose new terms to be added:
    • to the metadata vocabulary: the manufacturer can propose a new term if he/she believes that one or more features of the product he/she is adding do not fit into the current vocabulary. The user can propose both a new term (e.g. speech recognition) or an entire new “cluster” (e.g. activation methods) with one or more terms in it.
    • to the registry of common terms <this functions is already in place in the current SAT>

There will be two entry point for proposing new items to the vocabulary: in the homepage and in the page for entering product details (i.e. while the manufacturer is entering the data he/she finds out that a new item is needed in the vocabulary).

Proposed terms are automatically compared with existing terms in the vocabulary and a list of “similar” terms is presented (something like a “did you mean…” function). The user can then select one of the “similar” terms or stay with his/her decision of submitting a new term. For example if the user wants to suggest the new term “speech input” the system founds that a term “speech recognition” exists and present it to the user.

The tool should be made “lively”. If technically possible it should suggest the terms for product description (taking them from the metadata vocabulary) while the manufacturer enters the data.

When new terms are proposed the system administrator receive an alert and goes to a page where he/she can validate the terms and decide whether they should be added to the vocabulary.  Terms that are not added to the vocabulary are taken in consideration for “synonyms” (e.g. “voice recognition” can be added as a synonym (alias) of “speech recognition”).

There will betwo kinds of administrators: one for the metadata vocabulary and one for the common term registry (that refers to the ISO 24752 group)

The proponent is always given a feedback in both cases that the proposal has been accepted or not.

When submitting a new item for the metadata vocabulary the user has to eneter:

  • The name of the proposed term (e.g. voice input)
  • The Cluster it falls into (e.g. activation methods). If no cluster are appropriate, he/she can add a new one
  • A short description of the new feature to be added (e.g. for voice recognition “activation of specific commands through the voice”). In case a new cluster is proposed, a description of the new cluster.
  • The product typologies for which this item is needed (e.g. mobile phones)
  • A link to a webpage describing the product for which the new term is needed.
  • The email of the proponent (in case he is logged to the system this is not needed)

The information is stored on a database and the system administrator is alerted that a new proposal is available.

The administrator access the webpage where the proposal are collected and decide whether the new term is to be added. If rejected the term can be added as synonym of an existing term (this means that we need to manage synonyms).

If the term is accepted a notice is sent to the proponent. If the term is rejected the administrator has to provide a reason and send it to the proponent.

Visual simulation of the toolbox

A manufacturer  that wants to add his product (or app) to the Cloud4all infrastructure logs in to the SAT tool and clicks on “enter new application

Enter new app.png

First step: the manufacturer enters the product type. A list of possible types is returned. If the manufacturer believes a new type is needed he can propose a new one.

Metadata first.png

Second step: the manufacturer enters the basic product information. He can also use the “load EASTIN properties” function after having entered the product name.

Metadata second.png


Third step: the manufacturer enters the “technical details” of his product by selecting the appropriate terms of the metadata vocabulary (based on the EASTIN taxonomy).

If he believes that a term needed to describe his solution is missing he can propose a new term.

He can also propse an entire new “cluster” (or group) of terms (e.g. “processing methods”)

Metadata third.png



After the manufacturer has entered a proposal for a new item (he has clicked on “propose new item”). The tool make a lexicographic analysis and propose a list of items that are possibly similar to the one proposed.

The manufacturer can post his proposal as

• a synonim (alias) of an existing term or
• as a new term
Existing items similar.jpg



Forth step: the manufacturer enters the specific settings of his app and align this to the terms of the “common term registry”

If for a specific setting an appropriate alignment with common term cannot be found, the manufacturer can propose the term to be added to the registry.

<THIS FUNCTION IS ALREADY IN PLACE IN THE CURRENT SAT TOOL.>

Propose new registry item.png

The“taxonomy administator” will have to access a page where he/she will find all the proposals that have been sbmitted. Administrator can accept, modify and accept, or reject the proposals.

Metadata admin view.png

Wiki Categories