The Whispers Metadata Service: The Witness Relocation Program for Metadata

Pipeliner

David Fiander, Kristina Aston, William Wueppelmann, Tito Sierra

What is it?

What is the Service?

Standardized way to initiate translation from one metadata format to another using web services.

Why is it called The Whispers?

Chinese Whispers, also known as The (broken) Telephone Game ... [Wikipedia]

 

How it happens?

The theory, anyways:

  1. Requester packages metadata record into an XML request along with the desired output format.
  2. Server receives request, performs needed translation.
  3. Server returns an XML message with status information and the encoded transformed record.
  4. Requestor extracts and unpacks metadata record.

Structure of a Request

metadataTransformationRequest

 

The request indicates the format of the original metadata record and the desired target format. The record itself is encoded using Base64 so that there can be no conflicts with the XML request container.

Structure of a Response

metadataTransformResponse

The server returns an HTTP-style numeric code to indicate whether the request was successful or not and, if not, why not. 

 

User would need to compare the losses all along the way between A and D. The API would provide documentation that would show the losses between each step of the translations in a user-friendly way, via a URL,  that would describe the transformation process.

 

Issues and Future Roadmap