Date: Thu, 28 Mar 2024 15:44:09 -0400 (EDT) Message-ID: <387993752.28802.1711655049330@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_28801_768822288.1711655049330" ------=_Part_28801_768822288.1711655049330 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Feb 25, 2014
Question from Stefanie of whether we will ever be able to move to non-fl= at metadata. Example of dcterms.publisher and need to use URI, as specified= in domain and range. If only providing a string, will need to use dc.publi= sher rather than dcterms.publisher. Bram suggests could store a URI but wou= ld need functionality of human lookup name for that URI, for display. These= values would not necessarily reside in the metadata but in some other inde= x. Maureen suggests need to supercede and maybe replace the old mappings-- = more current mapping would indicate that both DCTERMS and DC ship with DSpa= ce. Do need to address the mapping document.
Bram asks about QDC in the DC community. Stefanie reports that most proj= ects use DCTERMS alongside DC. Did some work on application profile for RDF= representation, published this year, using DC, DCTERMS, and terms from oth= er vocabularies, like VIVO, to describe objects. Use of MARC relator codes = (http://id.loc.gov/vocabulary/relators.html) and U= RIs for qualified contributors. References user guide: http://wiki.dublincore.org/index.php/User_Guide Need a mix&a= mp;match approach, ability to pull in terms beyond Dublin Core. Bibframe, r= eplacement for MARC, working on vocabularies for bibliographic data. Focus = on work & instance as a version/simplification of FRBR. In RDF: qualifi= er =3D subproperty. MARC relator code expressed as subproperty of creator o= r contributor.
Discussion of whether RDF needs to be integrated into DSpace internal fo= rmat or not. Possibility, instead, of capability to crosswalk RDF out of in= ternal format. Stefanie indicates that this is a matter of preference-- som= e prefer that the internal format of the database be distinct from the expo= rt format (makes it more flexible to transform to DC, DC RDF, MODS, etc.). = Not absolutely fixed on the format-- more flexible and allows for transform= ation. But have to make sure that what is in the data is what you really ne= ed to generate RDF. Need to be able to store URIs and MARC relator codes in= internal format. Others say it is easier to keep data in the format you in= tend for distribution. Points us to German National Library and data transf= ormation efforts (https://wiki.dnb.de= /pages/viewpage.action?pageId=3D68061169). Recommendation is "rather fl= at" but seen as "first step on our way to good linked data having in mind t= he Europeana Data Model... and BIBFRAME."
Stefanie will look at changes her colleagues have made to the original D= Space registry.
For Dublin Core, possibility of discussing this proposal at the Librarie= s community meeting.
Time | Item | Who | Notes |
---|---|---|---|
|
|||