Re: [dspace-tech] the elements of DIM
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.r
Re: [dspace-tech] Re: [Dspace-tech] Request copy feature
Hello, the texts which appear in th UI are from message catalogues. These are different for JSPUI (incl. API) und XMLUI you can find instructions for both in the DSpace Documentation at: https://wiki.duraspace.org/display/DSDOC5x/Localization+L10n Best always state with which version and UI you are working. Hope that helps Claudia Jürgen Am 26.01.2017 um 08:02 schrieb Emmanuel Scaria: hi, i want to change the form label on this request copy of document page. Please give the suggestions regards Emmanuel -- 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 claudia.juer...@tu-dortmund.de 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 dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
Re: [dspace-tech] the elements of DIM
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 claudia.juer...@tu-dortmund.de 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 rec
[dspace-tech] the elements of DIM
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 === -- 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 dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
[dspace-tech] Collecting data about CRIS entities
Hi all Link for reference: https://wiki.duraspace.org/display/DSPACECRIS/How+to+collect+data+about+CRIS+entities I'm facing "the third way" described. My goal is to create and populate CRIS entities as part of the submission process and I must say that following the reference link is kind of messy. As far as I understand all modifications must be done in cris-plugin.xml but I keep getting this WARN: 2017-01-26 11:19:21,519 WARN org.dspace.core.PluginManager @ Cannot find named plugin for interface=org.dspace.content.authority.ChoiceAuthority, name="null" Taking a look at my dspace.cfg Authority Control Settings is all untouched from fresh install. Attached the file anyway. Another thing, when testing cris-plugin.xml with this configuration: <...> <.../> I get another WARN: 2017-01-26 12:38:05,628 WARN org.dspace.app.cris.util.ResearcherPageUtils @ Property grant not found Why does it look at ResearcherPageUtils? Can somebody provide another example on how to do it besides the two provided in the reference link? My system: DSpace-CRIS version 5_x_x downloaded and packaged the 10th of January. -- 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 dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout. # Authority Control Settings # plugin.named.org.dspace.content.authority.ChoiceAuthority = \ org.dspace.app.cris.integration.ORCIDAuthority = RPAuthority,\ org.dspace.content.authority.ItemAuthority = PublicationAuthority,\ org.dspace.content.authority.ItemAuthority = DataSetAuthority,\ org.dspace.app.cris.integration.ProjectAuthority = ProjectAuthority,\ org.dspace.app.cris.integration.OUAuthority = OUAuthority,\ org.dspace.app.cris.integration.DOAuthority = JOURNALAuthority,\ org.dspace.app.cris.integration.DOAuthority = EVENTAuthority,\ org.dspace.app.cris.integration.RPAuthorityForCRIS = RPAuthorityCRIS,\ org.dspace.app.cris.integration.ProjectAuthorityForCRIS = ProjectAuthorityCRIS,\ org.dspace.app.cris.integration.OUAuthorityForCRIS = OUAuthorityCRIS,\ org.dspace.app.cris.integration.DOAuthorityForCRIS = JOURNALAuthorityCRIS,\ org.dspace.app.cris.integration.DOAuthorityForCRIS = EVENTAuthorityCRIS,\ org.dspace.app.cris.integration.SOLRSuggestAuthority = SOLRSuggestAuthority authority.minconfidence = accepted ItemAuthority.reciprocalMetadata.dc.relation.publication = dc.relation.dataset choices.plugin.dc.relation.publication = PublicationAuthority choices.presentation.dc.relation.publication = lookup authority.controlled.dc.relation.publication = true cris.ItemAuthority.dc_relation_publication.filter = -dc.type:dataset choices.plugin.dc.relation.dataset = DataSetAuthority choices.presentation.dc.relation.dataset = lookup authority.controlled.dc.relation.dataset = true cris.ItemAuthority.dc_relation_dataset.filter = dc.type:dataset choices.plugin.dc.contributor.author = RPAuthority choices.presentation.dc.contributor.author = lookup authority.controlled.dc.contributor.author = true choices.plugin.dc.relation = ProjectAuthority choices.presentation.dc.relation = suggest authority.controlled.dc.relation = true choices.plugin.dc.description.sponsorship = OUAuthority choices.presentation.dc.description.sponsorship = suggest authority.controlled.dc.description.sponsorship = true choices.plugin.dc.relation.ispartof = JOURNALAuthority choices.presentation.dc.relation.ispartof = suggest authority.controlled.dc.relation.ispartof = true cris.DOAuthority.dc_relation_ispartof.filter = resourcetype_authority:crisjournals cris.DOAuthority.dc.relation.ispartof.new-instances = journals ItemCrisRefDisplayStrategy.publicpath.dc.relation.ispartof = journals choices.plugin.dc.relation.conference = EVENTAuthority choices.presentation.dc.relation.conference = suggest authority.controlled.dc.relation.conference = true cris.DOAuthority.dc_relation_conference.filter = resourcetype_authority:crisevents cris.DOAuthority.dc.relation.conference.new-instances = events ItemCrisRefDisplayStrategy.publicpath.dc.relation.conference = events
[dspace-tech] Re: dspace 5.6 doi
Hi Claudia, In the Cronjob we have /dspace/bin/dspace doi-organiser -u -q ; /dspace/bin/dspace doi-organiser -s -q ; /dspace/bin/dspace doi-organiser -r -q ; /dspace/bin/dspace doi-organiser -d -q. On the datacite site there is no record of new item, It seems that the system give a doi because with dspace doi-organiser -u I can see some item but on the "item detaiI" can't see doi sign. With DSpace 4 after a submission I could see in the item details the doi so now I don't know why the 5.6 doesn't work. Kind regards Massimiliano Il giorno martedì 24 gennaio 2017 14:50:37 UTC+1, Massimiliano CILURZO ha scritto: > > Dear All,. > We have a problem with doi datacite. > The system doesn't mint doi anymore. > This is the dspace.log > when use > dspace doi-organiser -u > > > 017-01-24 14:45:03,542 ERROR org.dspace.identifier.doi.DOIOrganiser @ It > wasn't possible to update this identifier: doi:10.143/unxx-689 Exceptions > code: CODE_NOT_SET > org.dspace.identifier.doi.DOIIdentifierException: DSO with type ITEM and > id 2492 already has DOI . Won't reserve DOI doi:10.143/unxxx-689 for it. > at > org.dspace.identifier.doi.DataCiteConnector.reserveDOI(DataCiteConnector.java:529) > at > org.dspace.identifier.doi.DataCiteConnector.updateMetadata(DataCiteConnector.java:681) > at > org.dspace.identifier.DOIIdentifierProvider.updateMetadataOnline(DOIIdentifierProvider.java:412) > at > org.dspace.identifier.doi.DOIOrganiser.update(DOIOrganiser.java:669) > at > org.dspace.identifier.doi.DOIOrganiser.runCLI(DOIOrganiser.java:265) > at > org.dspace.identifier.doi.DOIOrganiser.main(DOIOrganiser.java:82) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:226) > at > org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:78) > > Could you help me? > Thanks > Best regards > Massimiliano Cilurzo > > -- 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 dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
