Date: Thu, 28 Mar 2024 21:17:12 -0400 (EDT) Message-ID: <1935531155.29364.1711675032355@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_29363_1971787996.1711675032354" ------=_Part_29363_1971787996.1711675032354 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Go to LD4L Wiki Gateway
Archived
LD4L 2014, whic= h was the Linked Data for Libraries original grant running from 2014-2016, = has been completed. This page is part of the archive for that grant.<= /p>
BIBFRAME
The Bibliographic Framework Initiative (BIBFRA= ME) is an undertaking by the Library of Congress and the community to bette= r accommodate future needs of the library community. A major focus of the i= nitiative will be to determine a transition path for the MARC 21 exchange f= ormat to more Web based, Linked Data standards. Zepheira and The Library of= Congress are working together to develop a Linked Data model, vocabulary a= nd enabling tools / services for supporting this Initiative.
The BIBFRAME Initiative is the foundation for = the future of bibliographic description that happens on the web and in the = networked world. It is designed to integrate with and engage in the wider i= nformation community and still serve the very specific needs of libraries. = The BIBFRAME Initiative will bring new ways to: 1) differentiate clearly be= tween conceptual content and its physical/digital manifestation(s); 2) unam= biguously identify information entities (e.g., authorities); and 3) leverag= e and expose relationships between and among entities.
In a web-scale world, it is imperative to be a= ble to cite library data in a way that differentiates the conceptual work (= a title and author) from the physical details about that work's manifestati= on (page numbers, whether it has illustrations). It is equally important to= produce library data so that it clearly identifies entities involved in th= e creation of a resource (authors, publishers) and the concepts (subjects) = associated with a resource.
Although the BIBFRAME Initiative will instanti= ate a new way to represent and exchange bibliographic data =E2=80=93 that i= s, replace the Machine Readable Cataloging (MARC) format =E2=80=93 its scop= e is broader. As an initiative, it is investigating all aspects of bibliogr= aphic description, data creation, and data exchange. In addition to replaci= ng the MARC format, this includes accommodating different content models an= d cataloging rules, exploring new methods of data entry, and evaluating cur= rent exchange protocols. http://www.loc.gov/bibframe/=
Blacklight <= /p>
Blacklight is an open source Ruby on Rails gem= that provides a discovery interface for any Solr index. Blacklight provide= s a default user interface which is customizable via the standard Rails (te= mplating) mechanisms. Blacklight accommodates heterogeneous data, allowing = different information displays for different types of objects. Blacklight uses Apache Solr, an enterprise-scale index for its search engi= ne. Blacklight features faceted browsing, relevance based searching (with t= he ability to locally control the relevancy algorithms), bookmarkable items= , permanent URLs for every item, user tagging of items. = Blacklight is a component of the Hydra Project framework (see below) http://projectblacklight.org
Fedora Commons Repository So= ftware
Fedora (Flexible Extensible Digital Object Rep= ository Architecture) was originally developed by researchers at Cornell Un= iversity as an architecture for storing, managing, and accessing digital co= ntent in the form of digital objects inspired by the Kahn and Wilensky Fram= ework. Fedora defines a set of abstractions for expressi= ng digital objects, asserting relationships among digital objects, and link= ing "behaviors" (i.e., services) to digital objects.
The Fedora Repository Project (i.e., Fedora) i= mplements the Fedora abstractions in a robust open source software system.<= span> Fedora provides a core repository service (exposed as we= b-based services with well-defined APIs). In addit= ion, Fedora provides an array of supporting services and applications inclu= ding search, OAI-PMH, messaging, administrative clients, and more.&nb= sp; Fedora provides RDF support and the repository software is integ= rated with semantic triple store technology, including the Mulgara RDF data= base. Fedora helps ensure that digital content is durable by providing feat= ures that support digital preservation.
The Fedora Commons refers to the community sur= rounding the Fedora Repository Project. This community j= oins together with common needs, use cases, and projects. The Fedora Commons community is very active in producing additional tools= , applications, and utilities that augment the Fedora repository. Many of t= hese creations are available to the entire community as open source.=
The Fedora Repository software has been instal= led by institutions, worldwide, to support a variety of digital content nee= ds. The Fedora Repository is extremely flexible and can = be used to support any type of digital content. Th= ere are numerous examples of Fedora being used for digital collections, e-r= esearch, digital libraries, archives, digital preservation, institutional r= epositories, open access publishing, document management, digital asset man= agement, and more. The Fedora Repository software is a component of the Hyd= ra Project Framework (see below). http://fedora-common= s.org
Hydra Project
Hydra is a repository solution that is being u= sed by institutions on both sides of the North Atlantic to provide access t= o their digital content. Hydra provides a versatile and = feature-rich environment for end-users and repository administrators alike.= Hydra is a large, multi-institutional collaboration. Th= e project gives like-minded institutions a mechanism to combine their indiv= idual repository development efforts into a collective solution with breadt= h and depth that exceeds the capacity of any individual institution to crea= te, maintain or enhance on its own. Hydra is an ecosystem of components tha= t lets institutions deploy robust and durable digital repositories (the bod= y) supporting multiple =E2=80=9Cheads=E2=80=9D: fully-featured digital asse= t management applications and tailored workflows. Its pr= inciple platforms are the Fedora Commons repository software, Solr, Ruby on= Rails and Blacklight.
The Hydra Project was founded in 2008 by: Stan= ford University, University of Virginia, University of Hull, Fedora Commons= (now part of DuraSpace), and quickly augmented by MediaShelf LLC. These fi= ve founding partners are still very active and are the current members of t= he Hydra Steering Group.
Additional partners have formally committed th= emselves to support and further Hydra=E2=80=99s work: University of Notre D= ame, Northwestern University, Columbia University, Penn State University, I= ndiana University, London School of Economics and Political Science, Rock a= nd Roll Hall of Fame, The Royal Library of Denmark, Data Curation Experts, = WGBH, Boston Public Library, Duke University, Yale University, and Virginia= Tech. Further institutions are working with Hydra and its components. In time we hope that they will choose to join the formal Hyd= ra Partners. Amongst them: Spoken Word Services (Glasgow= Caledonian University), University College Dublin, University of Illinois = at Urbana-Champaign, The Digital Repository of Ireland, Museum of the Perfo= rming Arts (MAE) of the Theatre Institute of Barcelona, Johns Hopkins Unive= rsity, Tufts University, and Cornell University. http://projecthydra.org
ORCID
ORCID is an open, non-profit, community-driven= effort to create and maintain a registry of unique researcher identifiers = and a transparent method of linking research activities and outputs to thes= e identifiers. ORCID is unique in its ability to reach across disciplines, = research sectors and national boundaries. It is a hub that connects researc= hers and research through the embedding of ORCID identifiers in key workflo= ws, such as research profile maintenance, manuscript submissions, grant app= lications, and patent applications.
ORCID provides two core functions: (1) a regis= try to obtain a unique identifier and manage a record of activities, and (2= ) APIs that support system-to-system communication and authentication. ORCI= D makes its code available under an open source license, and will post an a= nnual public data file under a CC0 waiver for free download. = span>
The ORCID Registry is available free of charge= to individuals, who may obtain an ORCID identifier, manage their record of= activities, and search for others in the Registry. Organizations may becom= e members to link their records to ORCID identifiers, to update ORCID recor= ds, to receive updates from ORCID, and to register their employees and stud= ents for ORCID identifiers. http://orcid.org<= /span>
Stanford Linked Data Worksho= p
The Stanford University Libraries and Academic= Information Resources (SULAIR) with the Council on Library and Information= Resources (CLIR) conducted at week-long workshop from 27 June=E2=80=931 Ju= ly 2011 on the prospects for a large scale, multi-national, multi-instituti= onal prototype of a Linked Data environment for discovery of and navigation= among the rapidly, chaotically expanding array of academic information res= ources. As preparation for the workshop, CLIR sponsored a survey by Jerry P= ersons, Chief Information Architect emeritus of SULAIR that was published o= riginally for workshop participants as background to the workshop and is no= w publicly available. The original intention of the workshop was to devise = a plan for such a prototype. However, such was the diversity of knowledge, = experience, and views of the potential of Linked Data approaches that the w= orkshop participants turned to two more fundamental goals: building common = understanding and enthusiasm on the one hand and identifying opportunities = and challenges to be confronted in the preparation of the intended prototyp= e and its operation on the other. In pursuit of those objectives, the works= hop participants produced:
1. <= span>a value statement addressing the question of why a Linked Data approac= h is worth prototyping;
2. = a manifesto for Linked Libraries (and Museums and Archives and =E2=80= =A6);
3. = an outline of the phases in a life cycle of Linked Data approaches;= span>
4. = a prioritized list of known issues in generating, harvesting & us= ing Linked Data;
5. = a workflow with notes for converting library bibliographic records an= d other academic metadata to URIs;
6. = examples of potential =E2=80=9Ckiller apps=E2=80=9D using Linked Data= : and
7. a list of next steps and potential projects.
A full repo= rt on the workshop can be found at http://lib.stanford.edu/files/Stanford_Linke= d_Data_Workshop_Report_FINAL.pdf
VIVO
VIVO is an open community, an information mode= l, and an open source semantic web application supporting the advancement o= f research and scholarship by integrating and sharing information about res= earchers and scholars, their activities, and their outputs both within a si= ngle institution and across broad, distributed networks. VIVO is fundamenta= lly interdisciplinary; it enables and promotes the discovery of research an= d scholarship across traditional boundaries of geography, organization stru= cture and type, academic or clinical or applied domain, technology, languag= e, and culture. There is a diverse set of activities associated with the VI= VO project, across federal agencies, academic institutions, professional so= cieties, and data providers, as well as a variety of efforts with the Seman= tic Web and ontology development communities. VIVO was originally funded by= Cornell University and the National Institutes of Health (U24 RR029822) an= d is currently a community-supported incubator project under the DuraSpace = umbrella. http://vivoweb.org
In addition to =
the related efforts we have already mentioned, we are very interested in wo=
rking with and integrating other Linked Data efforts and existing identifie=
r and taxonomy efforts. Cornell is a contributor to the Social Networks and=
Archival Context (SNAC) effort [1]=
, and this is exactly the kind of additional contextu=
al value that we would like to bring to information resources. We would als=
o like to look at opportunities to leverage other EAD and finding aid infor=
mation to create structured context for information resources, for example =
by linking to historical events. The VIVO/Vitro framework that we will be u=
sing also supports linkage to standard external vocabularies (e.g., UMLS [2] , AGROVOC [3] , NALT =
[4] , and LCSH [5] ) and authorit=
y services such as LC Name Authority File =
[6] and VIAF =
[7] . We are tracking NISO Bibliographic Roadma=
p [8] process=
, and we will seek to engage with that effort in any way that is appropriat=
e.
<= span class=3D"MsoFootnoteReference"> [1] http://socialarchive.iath.virginia.edu/
<= span class=3D"MsoFootnoteReference"> [2] http://link.informatics.stonybrook.edu/um= ls/
<= span class=3D"MsoFootnoteReference"> [3] http://aims.fao.org/standards/a= grovoc/linked-open-data
<= span class=3D"MsoFootnoteReference"> [4] http://www.nal.usda.gov/news/NALT_LOD.shtm= l
<= span class=3D"MsoFootnoteReference"> [5] http://id.loc.gov/authorities/subjects.htm= l
<= span class=3D"MsoFootnoteReference"> [6] http://id.loc.gov/authorities/names.html<= /p>
<= span class=3D"MsoFootnoteReference"> [7] http://viaf.org
<= span class=3D"MsoFootnoteReference"> [8] http://www.niso.org/topics/tl/Bibl= iographicRoadmap/