Tag: Structure

  • Hierarchypedia

    What’s your sense?

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    0

  • Because MARC has different fields than MODS decisions…

    Because MARC has different fields than MODS, decisions must be made about where to put the data into MODS. This type of “translating” from one format to another is often called “metadata mapping” or “field mapping”.

    What a name! Schema crosswalk!

    A schema crosswalk is a table that shows equivalent elements (or “fields”) in more than one database schema. It maps the elements in one schema to the equivalent elements in another schema.

    That’s what I am doing. Schema crosswalk!

    Field Mapping.

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    0

  • Data integration systems require semantic integration before any…

    Data integration systems require semantic integration before any services can be provided. Hence, although there is not a single schema to which all the data conforms and the data resides in a multitude of host systems, the data integration system knows the precise relationships between the terms used in each schema.

    What are the matching and mapping generation techniques?

    The aim is to reduce the effort required to set up a data integration system by relying on existing matching and mapping generation techniques

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    0

  • Hmm one more term I am getting closer…

    Hmm, one more term. I am getting closer. Semantic Integration. That’s what I am supposed to do.

    From wikipedia:

    From the industry use case, it has been observed that the semantic mappings were performed only within the scope of the ontology class or the datatype property. These identified semantic integrations are (1) integration of ontology class instances into another ontology class without any constraint, (2) integration of selected instances in one ontology class into another ontology class by the range constraint of the property value and (3) integration of ontology class instances into another ontology class with the value transformation of the instance property. Each of them requires a particular mapping relationship, which is respectively: (1) equivalent or subsumption mapping relationship, (2) conditional mapping relationship that constraints the value of property (data range) and (3) transformation mapping relationship that transforms the value of property (unit transformation). Each identified mapping relationship can be defined as either (1) direct mapping type, (2) data range mapping type or (3) unit transformation mapping type.

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    0

  • Like we are fools yes we have been…

    Like we are fools, yes we have been fools, we have been sold platform-like solutions to present our non-platform ecommerce businesses. Actually those who sell may not understand the difference between the structures of platform based ecommerce and non-platform ecommerce. Have you given it any thought?

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    0

  • Aah It takes to figure n express all…

    Aah! It takes to figure n express all this. Platform-based ecommerce is different from non-platform based ecommerce.

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    0

  • Meta talk structure blueprints no one on social…

    Meta-talk, structure, blueprints no one on social media to enjoy that with me. Hammering is what they prefer.

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    0