Build a Learning Map

How does this work?
Authenticated users can assemble nodes from the Competency Index into Learning Maps, which represent logical sequences of competencies for use in defining formal curriculum structures or as personalized pathways created by instructors or learners as records of progress.

To build a Learning Map, select arrows at left to expand nodes of the Competency Index and view any child nodes below them. Select a node's Add to Map >> link to place it in sequence within the Learning Map at right. Continue adding nodes in the sequence that best suits your purpose for the map, then enter a unique name and select Save.

Click the up or down arrows at right of the node listing to modify the sequence, then select Save to update.

<< Show all Learning Maps

Learning Maps Listing

Learning Map: Competencies for Archivists

What's This?
Authenticated users can assemble nodes from the Competency Index into Learning Maps, which represent logical sequences of competencies for use in defining formal curriculum structures or as personalized pathways created by instructors or learners as records of progress.
For quickly getting archivists up-to-speed with Linked Data so that their digital collections can be published and shared.

Understands that Linked Data (2006) extended the notion of a web of documents (the Web) to a notion of a web of finer-grained data (the Linked Data cloud).

69 resources

Knows the "five stars" of Open Data: put data on the Web, preferably in a structured and preferably non-proprietary format, using URIs to name things, and link to other data.

66 resources

Knows that anything can be named with Uniform Resource Identifiers (URIs), such as agents, places, events, artifacts, and concepts.

17 resources

Understands that a "real-world" thing may need to be named with a URI distinct from the URI for information about that thing.

8 resources

Knows the subject-predicate-object component structure of a triple.

46 resources

Understands the RDF abstract data model as a directed labeled graph.

33 resources

Distinguishes the RDF abstract data model and concrete serializations of RDF data.

41 resources

Reuses published properties and classes where available.

32 resources

Coins namespace URIs, as needed, for any new properties and classes required.

14 resources

Recognizes the desirability of a published namespace policy describing an institution's commitment to the persistence and semantic stability of important URIs.

6 resources

Publishing RDF vocabularies

33 resources

Understands the typical publication formats for RDF vocabularies and their relative advantages

4 resources

Understands that to be "dereferencable", a URI should be usable to retrieve a representation of the resource it identifies.

21 resources

Cleans a dataset by finding and correcting errors, removing duplicates and unwanted data.

17 resources

Creating RDF data

44 resources

Knows the SPARQL 1.1 Graph Store HTTP protocol for updating graphs on a web server (in "restful" style).

14 resources