Dear Claudia,
Thanks for yuor suggestions.
I'll on a sandbox server.
Best regards
Massimiliano
Il giorno mercoledì 20 febbraio 2019 15:24:35 UTC+1, Claudia Jürgen ha
scritto:
>
> Hi Massimiliano,
>
> I would always work with a instance first, for all kinds of changes.,
> unless very small cosmetic ones.
> Our procedure is to create a git branch for the feature and work with it
> on a test instance until it is ready to be merged and deployed in
> production.
> In case of doi registration, you can get a test prefix from you provider
> and work with the datacite test server.
> see https://support.datacite.org/docs/create-a-client-in-fabrica-test
>
> Hope this helps
>
> Claudia Jürgen
>
> Am 19.02.2019 um 16:40 schrieb Massimiliano CILURZO:
> > Hi Claudia,
> > Ok but the system is in production accoding to you is safe to re
> build
> > and deploy?
> > Thanks
> > Best regards
> > Massimiliano
> >
> > Il giorno martedì 19 febbraio 2019 16:06:00 UTC+1, Claudia Jürgen ha
> > scritto:
> >> Hello Massimiliano,
> >>
> >> if you change something in the source code you got to build and deploy
> >> your application again.
> >>
> >> Hope this helps
> >>
> >> Claudia Jürgen
> >>
> >>
> >> Am 19.02.2019 um 14:11 schrieb Massimiliano CILURZO:
> >>> Dear Cluadia,
> >>> I have changed to Element identifier = new
> Element("identifier",
> >>> "http://datacite.org/schema/kernel-3";);
> >>> In DataCiteConnector.java.
> >>> According to you I have to restart the system, after this change?
> >>> Thanks
> >>> Regards
> >>> Massimiliano
> >>>
> >>> Il giorno martedì 19 febbraio 2019 13:02:39 UTC+1, Claudia Jürgen ha
> >>> scritto:
> >>>> Hello Massimiliano,
> >>>>
> >>>> as Mark already pointed out there is the issue for 5.x for the schema
> >>>> being hardcoded see:
> >>>> https://jira.duraspace.org/browse/DS-4044
> >>>> in
> >>>>
> >>>>
> >>
> https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-api/src/main/java/org/dspace/identifier/doi/DataCiteConnector.java#L1039
>
> >>>> Hope this helps
> >>>>
> >>>> Claudia Jürgen
> >>>>
> >>>>
> >>>>
> >>>> Am 19.02.2019 um 12:52 schrieb Massimiliano CILURZO:
> >>>>> Dear Claudia,
> >>>>> The dc.identifier.uri is present in every item.
> >>>>> And till 2 weeks ago the doi's were mint with the schema 2.2.
> >>>>> Now our server doesn't mint any DOI, even with the new schema 3.
> >>>>> If I do /dspace/bin/dspace doi-organiser -l after inserting a new
> >>>> item.
> >>>>> There isn't new doi.
> >>>>> Thanks
> >>>>> Best regards
> >>>>> Massimiliano
> >>>>>
> >>>>> Il giorno martedì 19 febbraio 2019 10:01:52 UTC+1, Claudia Jürgen ha
> >>>>> scritto:
> >>>>>> Hello Massimiliano,
> >>>>>>
> >>>>>> you need not add dc.identifier.uri (not doi). This is done prior to
> >>>>>> actually registering a doi with datacite, depending on the status:
> >>>>>>
> >>>>>>
> >>
> https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-api/src/main/java/org/dspace/identifier/DOIIdentifierProvider.java#L69
>
> >>>>>> A newly ingested item will have the status 7:
> >>>> UPDATE_BEFORE_REGISTRATION
> >>>>>> After having run doi-organiser -u this will turn to 1:
> >> TO_BE_REGISTERED
> >>>>>> The metadata dc.identifier.uri is set in this process
> >>>>>>
> >>>>>>
> >>
> https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-api/src/main/java/org/dspace/identifier/DOIIdentifierProvider.java#L881
>
> >>>>>> You can check items queued with:
> >>>>>> [dspace]/bin/dspace doi-organiser -l
> >>>>>>
> >>>>>> In the doi table you will see the status of the documents.
> >>>>>> And check the logs whether something went wrong during registration
> >> and
> >>>>>> you ended up with an inconsistent status.
> >>>>>>
> >>>>>> Hope this helps
> >>>>>>
> >>>>>> Claudia Jürgen
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Am 19.02.2019 um 09:19 schrieb Massimiliano CILURZO:
> >>>>>>
> >>>>>> Dear Claudia,
> >>>>>> In this item there is no DOI but in the item submission form
> the
> >>>> field
> >>>>>> dc.identifier.doi is present.
> >>>>>> And generally I leave this field blank, than after the submission
> and
> >>>> doi
> >>>>>> url appear on the item page after using
> >>>>>> /dspace/bin/dspace doi-organiser -u
> >>>>>> Is this correct or I'm doing wrong?
> >>>>>>
> >>>>>>
> >>>>>> Thanks
> >>>>>> Best regards
> >>>>>> Massimiliano
> >>>>>>
> >>>>>> Il giorno venerdì 15 febbraio 2019 12:51:19 UTC+1, Claudia Jürgen
> ha
> >>>>>> scritto:
> >>>>>>
> >>>>>> P. S.
> >>>>>>
> >>>>>> best try the check first this one:
> >>>> http://elea.unisa.it/xmlui/handle/10556/2854?show=full <
> >>>>
> >>
> http://www.google.com/url?q=http%3A%2F%2Felea.unisa.it%2Fxmlui%2Fhandle%2F10556%2F2854%3Fshow%3Dfull&sa=D&sntz=1&usg=AFQjCNHwu6qjaTVQLETOX5cadO47QinA9A>
>
>
> >>
> >>>> <
> >>>>
> >>
> http://www.google.com/url?q=http%3A%2F%2Felea.unisa.it%2Fxmlui%2Fhandle%2F10556%2F2854%3Fshow%3Dfull&sa=D&sntz=1&usg=AFQjCNHwu6qjaTVQLETOX5cadO47QinA9A>
>
>
> >>
> >>>>>> this seems not to have dc.identifier.doi which is necessary for
> >>>>>> registration or update
> >>>>>>
> >>>>>> So try
> >>>>>> [dspace]/bin/dspace dsrun
> >>>>>> org.dspace.content.crosswalk.XSLTDisseminationCrosswalk DataCite
> >>>>>> 10556/2854 [path/to/output]
> >>>>>>
> >>>>>> Hope this helps
> >>>>>>
> >>>>>> Claudia Jürgen
> >>>>>>
> >>>>>> Am 15.02.2019 um 11:01 schrieb Claudia Jürgen:
> >>>>>>
> >>>>>> Hello Massimiliano,
> >>>>>>
> >>>>>> we are running DSpace 5.x with DataCite 4.1 (heavily relying on our
> >> own
> >>>>>> metadata and thus not yet backported to DSpace).
> >>>>>> Prior to this we had DataCite 3.1 with no problems.
> >>>>>>
> >>>>>> You can test your crosswalk by crosswalking an item with:
> >>>>>> [dspace]/bin/dspace dsrun
> >>>>>> org.dspace.content.crosswalk.XSLTDisseminationCrosswalk DataCite
> >>>>>> [YOUR-HANDLE] [path/to/output]
> >>>>>> and then validating the resulting xml
> >>>>>> That is allways advisable prior to changing the one in production.
> >>>>>>
> >>>>>> The difference between 5.x and 6.x is that in 6.x some things like
> >> the
> >>>>>> namespace was made configurable which was prior hardcoded in the
> >>>>>> DataCiteConnector.
> >>>>>>
> >>>>>> Hope this helps
> >>>>>>
> >>>>>> Claudia Jürgen
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Am 14.02.2019 um 18:55 schrieb Tim Donohue:
> >>>>>>
> >>>>>> Hi Massimiliano,
> >>>>>>
> >>>>>> The main error message there seems to be this one:
> >>>>>>
> >>>>>> While reserving the DOI doi:10.10xxx/un**-1194, we got a http
> status
> >>>>>> code
> >>>>>> 422 and the message "This element is not expected. expected is one
> of
> >>>>>> ( { http://datacite.org/schema/kernel-3}identifier, {
> >>>> http://datacite.org/schema/kernel-3}creators, {
> >>>> http://datacite.org/schema/kernel-3}titles, {
> >>>> http://datacite.org/schema/kernel-3}publisher, {
> >>>> http://datacite.org/schema/kernel-3}publicationyear, {
> >>>> http://datacite.org/schema/kernel-3}subjects, {
> >>>> http://datacite.org/schema/kernel-3}contributors, {
> >>>> http://datacite.org/schema/kernel-3}dates, {
> >>>> http://datacite.org/schema/kernel-3}language, {
> >>>> http://datacite.org/schema/kernel-3}resourcetype ).
> >>>>>> That error is saying that the DataCite API seems to be returning a
> >> 422
> >>>>>> (Unprocessable Entity) Response with an error message that says
> "This
> >>>>>> element is not expected" and a list of expected elements.
> >>>>>>
> >>>>>> I'm going to admit, I'm not familiar myself with the DataCite
> service
> >>>>>>
> >>>>>> or
> >>>>>>
> >>>>>> this DOI connector in DSpace. (It was written & tested by other
> >>>>>> developers
> >>>>>> -- DSpace is a community-wide effort, and I'm unable to review
> every
> >>>>>> line
> >>>>>> of code.) It's possible either the patch you applied didn't full
> >>>>>>
> >>>>>> "work"
> >>>>>>
> >>>>>> for DSpace 5.6, or maybe there's another fix in DSpace 6.0 that I
> >>>>>> overlooked that provides compatibility with DataCite schema 3.x
> >>>>>>
> >>>>>> Does anyone else on this list have experience in using the DOI
> >>>>>>
> >>>>>> connector
> >>>>>>
> >>>>>> with DataCite Schema 3.x in either DSpace 6.x or 5.x? I'm
> wondering
> >> if
> >>>>>> someone else may have seen errors of this sort before, or perhaps
> can
> >>>>>> confirm that DSpace 6.x works fine with DataCite Schema 3.x?
> >>>>>>
> >>>>>> - Tim
> >>>>>>
> >>>>>> On Thu, Feb 14, 2019 at 9:56 AM Massimiliano CILURZO <
> >> mcil...@unisa.it
> >>>>>> <javascript:>>
> >>>>>>
> >>>>>> wrote:
> >>>>>>
> >>>>>>
> >>>>>> Dear Tim,
> >>>>>> I have tried the second option and updated to schema 3.1
> >> first.
> >>>>>> But the answer after
> >>>>>>
> >>>>>> /dspace/bin/dspace doi-organiser -u
> >>>>>>
> >>>>>> is this in dspace.log
> >>>>>> ERROR org.dspace.identifier.doi.DOIOrganiser @ It wasn't
> possible
> >> to
> >>>>>> update this identifier: doi:10.14273/unisa-937 Exceptions code:
> >>>>>> BAD_ANSWER
> >>>>>> org.dspace.identifier.doi.DOIIdentifierException: Unable to parse
> an
> >>>>>> answer from DataCite API. Please have a look into DSpace logs.
> >>>>>> at
> >>>>>>
> >>>>>>
> >>>>>>
> >>
> org.dspace.identifier.doi.DataCiteConnector.reserveDOI(DataCiteConnector.java:564)
>
>
> >>
> >>>>>> 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)
> >>>>>> 2019-02-14 16:43:43,985 WARN
> >>>>>> org.dspace.identifier.doi.DataCiteConnector
> >>>>>> @ While reserving the DOI doi:10.10xxx/un**-1194, we got a http
> >>>>>> status code
> >>>>>> 422 and the message "This element is not expected. expected is one
> >>>>>> of ( { http://datacite.org/schema/kernel-3}identifier, {
> >>>> http://datacite.org/schema/kernel-3}creators, {
> >>>> http://datacite.org/schema/kernel-3}titles, {
> >>>> http://datacite.org/schema/kernel-3}publisher, {
> >>>> http://datacite.org/schema/kernel-3}publicationyear, {
> >>>> http://datacite.org/schema/kernel-3}subjects, {
> >>>> http://datacite.org/schema/kernel-3}contributors, {
> >>>> http://datacite.org/schema/kernel-3}dates, {
> >>>> http://datacite.org/schema/kernel-3}language, {
> >>>> http://datacite.org/schema/kernel-3}resourcetype ). at line 3,
> >>>>>> column 0".
> >>>>>> 2019-02-14 16:43:43,985 ERROR
> org.dspace.identifier.doi.DOIOrganiser
> >>>>>> @ It
> >>>>>> wasn't possible to update this identifier: doi:10.14273/unisa-1194
> >>>>>> Exceptions code: BAD_ANSWER
> >>>>>>
> >>>>>> Could you help me to understand the reason?
> >>>>>> Thanks
> >>>>>> Best regards
> >>>>>> Massimiliano
> >>>>>>
> >>>>>>
> >>>>>> Il giorno martedì 12 febbraio 2019 19:23:47 UTC+1, Tim Donohue ha
> >>>>>> scritto:
> >>>>>>
> >>>>>>
> >>>>>> Hello Massimiliano,
> >>>>>>
> >>>>>> Since you are running DSpace 5.6, you'd have two options to get to
> >>>>>> DataCite v4.1 compatibility:
> >>>>>>
> >>>>>> - Either you should upgrade to DSpace 6.3 (the latest
> version
> >> of
> >>>>>> 6.x), and then apply this patch
> >>>>>> https://github.com/DSpace/DSpace/pull/2321
> >>>>>> - Or, you would need to apply *two* patches to DSpace 5.x.
> >>>>>>
> >>>>>> First,
> >>>>>>
> >>>>>> you'd have to apply the fixes to update to DataCite schema
> v3.1
> >> :
> >>>>>> https://github.com/DSpace/DSpace/pull/1197 (This is the
> fix
> >>>>>> that was
> >>>>>> included as part of 6.0). Then you would need to apply this
> >>>>>>
> >>>>>> patch:
> >>>>>>
> >>>>>> https://github.com/DSpace/DSpace/pull/2321
> >>>>>>
> >>>>>> You also may want to simply see if upgrading to DSpace 6.3 would
> >>>>>> *solve*
> >>>>>> the issues you are having. In your original email, it was unclear
> >>>>>> if you
> >>>>>> absolutely *must* be running DataCite schema v4.1, or if possibly
> >>>>>> DataCite
> >>>>>> schema v3.1 would work. So, honestly, my recommendation would be
> >>>>>> to first
> >>>>>> start up a test server with DSpace 6.3 on it to see if
> >>>>>> compatibility with
> >>>>>> DataCite schema 3.1 fixes the issues you are seeing. If so, you
> >>>>>> may not
> >>>>>> even need to apply the patch to update to DataCite schema 4.1. I
> >>>>>> cannot
> >>>>>> give advice myself on whether upgrading to DSpace 6.3 will solve
> >>>>>> the issue
> >>>>>> or not -- that's likely something you'd need to either test out
> >>>>>> yourself,
> >>>>>> or talk to the DataCite team about.
> >>>>>>
> >>>>>> - Tim
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Tue, Feb 12, 2019 at 12:12 PM Massimiliano CILURZO <
> >> mcil...@unisa.it>
> >>>>>> wrote:
> >>>>>>
> >>>>>>
> >>>>>> Dear Tim.
> >>>>>> I'm running DSpace 5.6 I could install this patch on it?
> >>>>>> I would like to try this patch, If you tell me that I could use it
> >>>>>> only
> >>>>>> on DSpace 6.0 I'll try it first on a test server with DSpace 6.0.
> >>>>>> If I can I'll try to help for this patch with some notes about it.
> >>>>>> Thanks
> >>>>>> Best regards
> >>>>>> Massimiliano
> >>>>>>
> >>>>>> Il giorno martedì 12 febbraio 2019 17:13:42 UTC+1, Tim Donohue ha
> >>>>>> scritto:
> >>>>>>
> >>>>>>
> >>>>>> Massimiliano,
> >>>>>>
> >>>>>> Just a follow-up to Mark's previous note. DSpace 6.x is using
> >>>>>> DataCite
> >>>>>> Schema 3.1 (so if you are seeing Schema 2.2, I'm assuming you
> >>>>>> aren't using
> >>>>>> the latest DSpace), see this update which was released in DSpace
> >>>>>> 6.0: https://jira.duraspace.org/browse/DS-2924
> >>>>>>
> >>>>>> As Mark notes, we have a pending update to DataCite Schema 4.1,
> >>>>>> which
> >>>>>> likely won't be released until 6.4 (at the earliest). If you are
> >>>>>> already
> >>>>>> running DSpace 6.x, this patch should be relatively easy to apply
> >>>>>> immediately. If you are able to help test this patch, then we'd
> >>>>>> appreciate
> >>>>>> it if you could add notes to the patch (in GitHub), as that will
> >>>>>> allow us
> >>>>>> to more easily approve/merge the change in time for 6.4. Again,
> >>>>>> here's
> >>>>>> where this patch is: https://github.com/DSpace/DSpace/pull/2321
> >>>>>>
> >>>>>> If you have further questions, let us know on this list.
> >>>>>>
> >>>>>> Tim
> >>>>>>
> >>>>>> On Mon, Feb 11, 2019 at 8:00 AM Mark H. Wood <mwood...@gmail.com>
> >>>>>> wrote:
> >>>>>>
> >>>>>>
> >>>>>> On Monday, February 11, 2019 at 4:23:53 AM UTC-5, Massimiliano
> >>>>>> CILURZO
> >>>>>>
> >>>>>> wrote:
> >>>>>>
> >>>>>> The DOI Datacite schema now is arrived to 4.1, we have on
> >>>>>> DSpace version 2.2 and it could have some problem with the new
> >>>>>> managemant
> >>>>>> software of DATACITE.
> >>>>>> With a schema version 2.2 it cuold be impossible to do an
> >>>>>> update via
> >>>>>> the "DOI DataCite Fabrica" system.
> >>>>>> So I would like to know if it is possible to update this schema
> >>>>>>
> >>>>>> to
> >>>>>>
> >>>>>> 4.1.
> >>>>>>
> >>>>>>
> >>>>>> There is a patch to upgrade to 4.0:
> >>>> https://github.com/DSpace/DSpace/pull/2321 which has not yet been
> >>>>>> merged.
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> All messages to this mailing list should adhere to the DuraSpace
> >>>>>> Code
> >>>>>> of Conduct: https://duraspace.org/about/policies/code-of-conduct/
> >>>>>> ---
> >>>>>> 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...@googlegroups.com.
> >>>>>> To post to this group, send email to dspac...@googlegroups.com.
> >>>>>>
> >>>>>> Visit this group at https://groups.google.com/group/dspace-tech.
> >>>>>> For more options, visit https://groups.google.com/d/optout.
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Tim Donohue
> >>>>>> Technical Lead for DSpace & DSpaceDirect
> >>>>>> DuraSpace.org | DSpace.org | DSpaceDirect.org
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> All messages to this mailing list should adhere to the DuraSpace
> >>>>>> Code of
> >>>>>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> >>>>>> ---
> >>>>>> 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...@googlegroups.com.
> >>>>>> To post to this group, send email to dspac...@googlegroups.com.
> >>>>>> Visit this group at https://groups.google.com/group/dspace-tech.
> >>>>>> For more options, visit https://groups.google.com/d/optout.
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Tim Donohue
> >>>>>> Technical Lead for DSpace & DSpaceDirect
> >>>>>> DuraSpace.org | DSpace.org | DSpaceDirect.org
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> All messages to this mailing list should adhere to the DuraSpace
> >>>>>> Code of
> >>>>>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> >>>>>> ---
> >>>>>> 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...@googlegroups.com <javascript:>.
> >>>>>> To post to this group, send email to dspac...@googlegroups.com
> >>>>>>
> >>>>>> <javascript:>.
> >>>>>>
> >>>>>> Visit this group at https://groups.google.com/group/dspace-tech.
> >>>>>> For more options, visit https://groups.google.com/d/optout.
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> 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...@tu-dortmund.de <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.
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> 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...@tu-dortmund.de <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.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Claudia Juergen
> >>>>>> Eldorado
> >>>>>>
> >>>>>> Technische Universität Dortmund
> >>>>>> Universitätsbibliothek
> >>>>>> Vogelpothsweg 76
> >>>>>> 44227 Dortmund
> >>>>>>
> >>>>>> Tel.: +49 231-755 40 43
> >>>>>> Fax: +49 231-755 40 32claudia...@tu-dortmund.de <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. *
> >>>>>>
> >>>> --
> >>>> 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...@tu-dortmund.de <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.
> >>>>
> >> --
> >> 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...@tu-dortmund.de <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.
> >>
>
> --
> 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...@tu-dortmund.de <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.
>
--
All messages to this mailing list should adhere to the DuraSpace Code of
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
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.
