Skip to content

Content metadata #14

@derega

Description

@derega

The curriculum story says that user should be aware why something is the way it is. One way to achieve this is to link learning material to the curriculum. One way to create this link is to use common metadata between learning material and curriculum. Learning material is tagged with keywords and same keywords are used inside the curriculum.

For this to work the metadata has to be shared between parties.

Sharing can happen with common APIs. Each service can ask all other services what kind of metadata keywords they support and are using.

Other way to do this is to have metadata sharing service. This service has a database which contains all keywords and all metadata of everything. This metadata repository can be updated by everyone and it keeps track who is doing what and why.

The database could be simple key/value store with graph functionality. Meaning the data can have complex hierarchies.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions