Discoverability
One of the biggest problems (IMHO) with OER is discovery of existing resources.
Domain Name System
DNS SRV
resource records are used to discover endpoints for various services.
Described in: RFC6335
Popular examples are SIP, LDAP, Minecraft and XMPP. This mechanism would mostly enable crawlers to discover them, since most users are not fluent in DNS. It is also unclear how the service is structured, if there where such an endpoint. As of today, several parties develop and maintain their own repositories.
Embedding Metadata in Websites
Enables Webcrawlers and their associated search engine providers to reason about website content. There is also the effort of the LRMI to provide schemes for educational courses. With Schema.org version 3.2, there is also schemes for educational content such as Course (or at least in pending, whatever that means).
RDFa has several limitations and it’s use is not exactly encouraged.
JSON-Linked Data (JSON-LD) usage is encouraged by most search engine providers. My problem with JSON-LD is, that it must be embedded by an inline script tad, practically duplicating most information already provided in the website.
Also, see: https://wiki.creativecommons.org/wiki/Web_Integration Most of that information is five years old, with most mentioned projects already disbanded. Which, sadly, seems to be the case for all projects regarding discovery and metadata (e.g. MozCC and it’s successor OpenAttribute).
OpenBadges
OpenBadges might help spread the existence of LMS and associated content, as they convey information about where they came from. Expected impact seems marginal, though.
Seems to be the only project still relevant in Mozilla’s educational activities. At least their user community seems to be active in recent days.
Standard development was moved to IMS Global, which will host an event on 2017-08-17 at the University of Michigan. Current draft is v2.0 and will be discussed there.
Content Sharing
General Media Metadata
XMP seems to be the de-facto standard for attaching metadata to various Multimedia Content
- https://api.creativecommons.org/docs/readme_15.html
- https://wiki.creativecommons.org/wiki/XMP_help_for_Adobe_applications
- https://wiki.creativecommons.org/wiki/Main_Page
Moodle already has support for files in external repositories, although citations for (CC) licensed media leaves all the work to users. Example: Merlot Integration is integradet by default, as well as Wikimedia
Dublin Core
https://en.wikipedia.org/wiki/Dublin_Core
Learning Object Metadata
RDF/XML (IEEE 1484.12.3 and IEEE 1484.12.4 respectively)
- https://www.imsglobal.org/metadata/index.html
- https://en.wikipedia.org/wiki/Learning_object_metadata
Sharable Content Object Reference Model
Interoperability format between LMS, sends calls through client side JavaScript, insecure by design.
xAPI (aka. SCORM v2)
- https://github.com/adlnet/xAPI-Spec/blob/master/xAPI.md
- https://github.com/adlnet/xAPI-Spec/blob/cc0dac339819be4e1984d5b68cf5285248b3f5c4/xAPI.md
- used in: in Beyond Delivery Modes and Apps: A Case Study on Mobile Blended Learning in Higher Education
Improves on many limitations of SCORM, like cheating participants, but still seems to be very complex. Centered around a key-value storage (Learning Record Store), aggregating Statements (Actor Verb Object) via RESTful services (https://experienceapi.com/tech-overview/#pt3). Communication is transfered in JSON.
Still unsure about xAPI is meant to deliver actual content or is just there for reporting.
usability/longevity
it seems that, like most broad standards, both SCORM and xAPI are difficult to use and hard to implement. xAPI states that Tapestry is one of the great and fruitful projects that is using xAPI. As many projects that implement SCORM, Tapestry already terminated their services.
Although the containers improve sharing content seamlessly, few people seem to actually use thr format for their content. This is also reflected in the Moodle FAQ for SCORM.
Used at:
MIT crosslinks
MIT OCW
Librarians and Libraries
Since librarians have most of these problems solved already, there are severel things that I learned when I spoke with them.
These are just keywords, that need expansion.
- Gemeinsame Normdatei
- National Library of medicine (medical metadata)
- library of congress (english metadata)
- Deutsche Nationalbibliothek
- Deutsche digitale Bibliothek
- http://leo-bw.de
- OPARU, uni ulm
- basiert auf DSPACE
- https://www.uni-ulm.de/einrichtungen/kiz/service-katalog/wid/publikationsmanagement/urheberrecht-richtig-zitieren/bildzitat/
- MODS/MADS Datenformat
- https://en.wikipedia.org/wiki/Metadata_standard
- Open Researcher and Contributor ID (ORCID)
Librarian Lingo
http://www.allegro-c.de/formate/sprache.htm
OPAC: Online Publich Access Catalogue. Letztendlich die öffentliche Schnittstelle über die Bibliotheksinformationen abgerufen werden können. List of next gen library catalogs
RDA: Resource Description and Access.
kein plan.
WorldCat
Globale, zentrale Bestandsliste aller teilnehmenden Bibliotheken. Bibliothek der Uni Ulm gibt ihre Bestandsliste an die Landeszentrale (Name vergessen), diese wiederum trägt dann bei Worldcat ein.
Verschlagwortung und Kategorisierung
Bibliographic Ontology Specification
Gemeinsame Normdatei
Liste der fachlichen Nachschlagewerke (299 Seiten) aus: Abeitshilfen zur GND
MARC21
Normalerweise im MARC21 Binärformat, aber auch als MARC21-XML verfügbar. DNB stellt auch Testdaten zur Verfügung. MARC21 Standard Documentation: http://www.loc.gov/marc/marcdocz.html und http://www.loc.gov/marc/specifications/specrecstruc.html
Es existieren Python2/3 Bibliotheken zum Arbeiten mit dem Format, diese weisen darauf hin, dass MARC21 ein Format ist, das nicht heuteigen Standards entspricht.
Beispielsweise ist ein Kritikpunkt, dass MARC21-records alle Informationen über ein Objekt enthalten, was dazu führt, dass die Informationen redundant in den Records verwaltet werden. Das Wiki, in dem die Kritik gesammelt wurde (letzter sinnvoller Beitrag ist vom 2011-11-17) hat einige Verweise zu den Designproblemen von MARC21. Auch die Anstrengungen der futurelib scheinen im Sand verlaufen zu sein.
Meines Erachtens ist, aus Sicht der Archivierung, die Redundanz hilfreich: so können die Records alleinstehend verwaltet werden, ohne Hinzunahme zusätzlicher Referenzen. Nachteilig ist bei dieser Form der Datenhaltung ggf. die fehlende Eindeutigkeit der Autoren, diese Datenstrukturen müssen zur Laufzeit reproduziert werden (keine Aussage, sondern eine Einschätzung).
- http://natlib.govt.nz/librarians/national-library-services/cataloguing
- http://datendienst.dnb.de/cgi-bin/mabit.pl?userID=testdat&pass=testdat&cmd=login
- http://www.dnb.de/DE/Standardisierung/Formate/MARC21/marc21_node.html
Citation and Identifiers
Persistent Identifier (PID)
mix between ID and location. Several different standards exist
Document Object Identifier
Wiki: https://en.wikipedia.org/wiki/Digital_object_identifier
Most research and resources should be accessible through a DOI. All documents with an associated DOI must be accessible through e.g. https://doi.org/10.1126/science.169.3946.635 (where 10.1126/science.169.3946.635 is the DOI). For more information about DOI Content Types: https://citation.crosscite.org/docs.html
Built upon the Handle System Infrastructure, EIDR is using the DOI System, also.
From crossref:
the South Park movie , “Bigger, Longer & Uncut” has a DOI: a) http://dx.doi.org/10.5240/B1FA-0EEC-C316-3316-3A73-L So does the pornographic movie, “Young Sex Crazed Nurses”: b) http://dx.doi.org/10.5240/4CF3-57AB-2481-651D-D53D-Q And the following DOI points to a fake article on a “Google-Based Alien Detector”: c) http://dx.doi.org/10.6084/m9.figshare.93964
- DOI Handbook
- Proxy API: Example https://doi.org/api/handles/10.18725/OPARU-4441
- Vocabulary Mapping Framework: Recommends Metadata Schemes based on used vocabulary, is dated (2009).
- Tools Section also seems to be pretty old.
- DataCite seems to be the provider for many universities. Have more services, needs more browsing.
ORCID
Open Researcher and Contributor ID
Uniform Resource Name
Archival Resource Key
https://confluence.ucop.edu/display/Curation/ARK
DOI vs. ARK: http://www.doi.org/doi_handbook/4_Data_Model.html#4.3.1
Persistent Uniform Resource Locator
Object Identifier
Permalink
Code and Data
How to create citeable github releases, through Zenodo: a service funded by CERN and horizon2020. Zenodo also provides citeable data storage up to 50 GB per file. When selecting a research data hoster the regisrty of research data repositories can be used to discover an appropriate provider.
Linked Data
The Web is not a glorified USB Stick
http://linkeddata.org/