Thank you very much Claudia, I am interested in the crosswalk, which happens when I ingest an object, described in a METS file (with some descriptive metadata in it).
>From what you are saying, I understand, that it is up to me to choose for my crosswalk: - to map some metadata to dc.rights.holder or to dcterms.rightsHolder - and in general --- to map to qualified DC (dc.xxx.xxx) or --- to map to DC terms (dcterms.xxx) or --- to map to a mixture of both (however ugly it is) Is this correct? I think I saw in the Manuel that there is a "tendency" in the DSpace project to move from qualified DC to DC terms. Do you know anything about this? Best regards Evgeni On Thursday, January 26, 2017 at 4:04:00 PM UTC+2, Claudia Jürgen wrote: > > Hello Evgeni, > > the metadata listed in item edit and all metadata fields usable in an > DSpace instance are in the metadata registry. > > On a fresh installation this is populated from: > https://github.com/DSpace/DSpace/tree/dspace-5.6/dspace/config/registries > > You can view/add/change metadata fields or even new schemata as > administrator via > Administer -> General Settings -> Metadata Registry > > The list of the default settings is quite stable, but there might be > changes, e.g. for the support of metadata for all objects new metadata > schemata were introduced like eperson. > > As DSpace supports metadata for not only items but also other DSpace > objects like > communites, collections, eperson ... > There are some "special" metadata schemata like eperson which are not > used for item metadata. > The DIM (DSpace intermediate metada) is just a legacy interim format > exposing all the item's metadata for internal use in crosswalking. > > In OAI the base for crosswalking is nowadays xoai not dim, if you are > working on a crosswalk there. > > Hope this helps > > Claudia Jürgen > > > > Am 26.01.2017 um 14:47 schrieb Evgeni Dimitrov: > > Hi, this is about DSpace 5.6. > > When I edit an item and add new metadata, I can select the kind of > metadata > > in a list (see bellow). I would like to know - what are this elements - > are > > they all elements of DIM? In terms of crosswalk - can they all be on the > > left side or on the right side of the crosswalk? Is this list supposed > to > > be stable from one version of DSpace to the next one? > > > > Best regards > > Evgeni > > > > ========================= > > dc.contributor.advisor, dc.contributor.author, dc.contributor.editor, > > dc.contributor.illustrator, dc.contributor.other, dc.contributor, > > dc.coverage.spatial, dc.coverage.temporal, dc.creator, > dc.date.accessioned, > > dc.date.available, dc.date.copyright, dc.date.created, dc.date.issued, > > dc.date.submitted, dc.date.updated, dc.date, dc.description.abstract, > > dc.description.provenance, dc.description.sponsorship, > > dc.description.statementofresponsibility, > dc.description.tableofcontents, > > dc.description.uri, dc.description.version, dc.description, > > dc.format.extent, dc.format.medium, dc.format.mimetype, dc.format, > > dc.identifier.citation, dc.identifier.govdoc, dc.identifier.isbn, > > dc.identifier.ismn, dc.identifier.issn, dc.identifier.other, > > dc.identifier.sici, dc.identifier.slug, dc.identifier.uri, > dc.identifier, > > dc.language.iso, dc.language.rfc3066, dc.language, dc.provenance, > > dc.publisher, dc.relation.haspart, dc.relation.hasversion, > > dc.relation.isbasedon, dc.relation.isformatof, dc.relation.ispartof, > > dc.relation.ispartofseries, dc.relation.isreferencedby, > > dc.relation.isreplacedby, dc.relation.isversionof, dc.relation.replaces, > > dc.relation.requires, dc.relation.uri, dc.relation, dc.rights.holder, > > dc.rights.license, dc.rights.uri, dc.rights, dc.source.uri, dc.source, > > dc.subject.classification, dc.subject.ddc, dc.subject.lcc, > dc.subject.lcsh, > > dc.subject.mesh, dc.subject.other, dc.subject, dc.title.alternative, > > dc.title, dc.type, dcterms.abstract, dcterms.accessRights, > > dcterms.accrualMethod, dcterms.accrualPeriodicity, > dcterms.accrualPolicy, > > dcterms.alternative, dcterms.audience, dcterms.available, > > dcterms.bibliographicCitation, dcterms.comformsTo, dcterms.conformsTo, > > dcterms.contributor, dcterms.coverage, dcterms.created, dcterms.creator, > > dcterms.date, dcterms.dateAccepted, dcterms.dateCopyrighted, > > dcterms.dateSubmitted, dcterms.description, dcterms.educationLevel, > > dcterms.extent, dcterms.format, dcterms.hasFormat, dcterms.hasPart, > > dcterms.hasVersion, dcterms.identifier, dcterms.instructionalMethod, > > dcterms.isFormatOf, dcterms.isPartOf, dcterms.isReferencedBy, > > dcterms.isReplacedBy, dcterms.isRequiredBy, dcterms.issued, > > dcterms.isVersionOf, dcterms.language, dcterms.license, > dcterms.mediator, > > dcterms.medium, dcterms.modified, dcterms.provenance, dcterms.publisher, > > dcterms.references, dcterms.relation, dcterms.replaces, > dcterms.requires, > > dcterms.rights, dcterms.rightsHolder, dcterms.source, dcterms.spatial, > > dcterms.subject, dcterms.tableOfContents, dcterms.temporal, > dcterms.title, > > dcterms.type, dcterms.valid, eperson.firstname, eperson.language, > > eperson.lastname, eperson.phone > > === > > > > -- > Claudia Juergen > Eldorado > > Technische Universität Dortmund > Universitätsbibliothek > Vogelpothsweg 76 > 44227 Dortmund > > Tel.: +49 231-755 40 43 > Fax: +49 231-755 40 32 > [email protected] <javascript:> > www.ub.tu-dortmund.de > > Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie > ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für > diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender > und vernichten Sie diese Mail. Vielen Dank. > Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen > ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher > Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines > solchen Schriftstücks per Telefax erfolgen. > > Important note: The information included in this e-mail is confidential. > It is solely intended for the recipient. If you are not the intended > recipient of this e-mail please contact the sender and delete this message. > Thank you. Without prejudice of e-mail correspondence, our statements are > only legally binding when they are made in the conventional written form > (with personal signature) or when such documents are sent by fax. > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
