[dspace-tech] Re: Strange behaviour of OAI in 6.2
Or may be this has something to do with another part of ColComFilter.java
which produces SolrQuery:
item.collections:(col_nls_87 OR col_nls_25523 OR com_nls_22332)
May be they should be separated as
item.collections:(col_nls_87 OR col_nls_25523) and
item.communities:(com_nls_22332)
or should be combined in one query like
item.collections:(col_nls_87 OR col_nls_25523) OR
item.communities:(com_nls_22332)
???
On Thursday, March 15, 2018 at 11:21:07 PM UTC+2, Evgeni Dimitrov wrote:
>
> May be it works the same in older versions too. I have not checked.
> I want to exclude from OAI the items under two collections and one
> community.
>
> I have in xoai.xml filter and condition:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> org.dspace.xoai.filter.ColComFilter
>
>
> col_nls_87
> col_nls_25523
> com_nls_22332
>
>
>
>
>
>
> and the main part of ColComFilter.java is:
>
> public boolean isShown(DSpaceItem item) {
> if (collectionSpecs == null) {
> getCollectionSpecs();
> }
>
> for (ReferenceSet rs : item.getSets()) {
> if (collectionSpecs.contains(rs.getSetSpec())) {
> return true;
> }
> }
> return false;
> }
>
>
>
> This works fine for the two collections:
>
>
> http://dspace6:8080/oai/request?verb=ListIdentifiers&metadataPrefix=oai_dc&set=col_nls_87
>
>
> http://dspace6:8080/oai/request?verb=ListIdentifiers&metadataPrefix=oai_dc&set=col_nls_25523
>
> return
>
> But it works differently for the community:
>
>
> http://dspace6:8080/oai/request?verb=ListIdentifiers&metadataPrefix=oai_dc&set=com_nls_22332
>
> returns a lot of identifiers:
>
> completeListSize="3731" (which is the size of the community)
>
> and many entries like:
>
> oai:dspace6:nls/27837
> 2017-12-14T09:52:31Z
> com_nls_22332
> com_nls_94
> col_nls_26938
>
>
> But for everyone of the identifiers in the list (I tried 20) the request
>
>
> http://dspace6:8080/oai/request?verb=GetRecord&metadataPrefix=oai_dc&identifier=oai:dspace6:nls/27837
>
> returns
> So that first OAI returns the ID in the list and second it says "the ID
> does not exist". The second part I expected because I want to exclude all
> items under this community. But the first part - the non empty list of IDs
> was unexpected.
>
> Is there an explanation of this or is this a defect in OAI?
>
>
>
--
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] Re: Strange behaviour of OAI in 6.2
Or may be this has something to do with another part of ColComFilter.java
which produces SolrQuery:
item.collections:(col_nls_87 OR col_nls_25523 OR com_nls_22332)
May be they should be separated as
item.collections:(col_nls_87 OR col_nls_25523) and
item.communities:(com_nls_22332)
or combined in one query like
item.collections:(col_nls_87 OR col_nls_25523) OR
item.communities:(com_nls_22332)
???
On Thursday, March 15, 2018 at 11:21:07 PM UTC+2, Evgeni Dimitrov wrote:
>
> May be it works the same in older versions too. I have not checked.
> I want to exclude from OAI the items under two collections and one
> community.
>
> I have in xoai.xml filter and condition:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> org.dspace.xoai.filter.ColComFilter
>
>
> col_nls_87
> col_nls_25523
> com_nls_22332
>
>
>
>
>
>
> and the main part of ColComFilter.java is:
>
> public boolean isShown(DSpaceItem item) {
> if (collectionSpecs == null) {
> getCollectionSpecs();
> }
>
> for (ReferenceSet rs : item.getSets()) {
> if (collectionSpecs.contains(rs.getSetSpec())) {
> return true;
> }
> }
> return false;
> }
>
>
>
> This works fine for the two collections:
>
>
> http://dspace6:8080/oai/request?verb=ListIdentifiers&metadataPrefix=oai_dc&set=col_nls_87
>
>
> http://dspace6:8080/oai/request?verb=ListIdentifiers&metadataPrefix=oai_dc&set=col_nls_25523
>
> return
>
> But it works differently for the community:
>
>
> http://dspace6:8080/oai/request?verb=ListIdentifiers&metadataPrefix=oai_dc&set=com_nls_22332
>
> returns a lot of identifiers:
>
> completeListSize="3731" (which is the size of the community)
>
> and many entries like:
>
> oai:dspace6:nls/27837
> 2017-12-14T09:52:31Z
> com_nls_22332
> com_nls_94
> col_nls_26938
>
>
> But for everyone of the identifiers in the list (I tried 20) the request
>
>
> http://dspace6:8080/oai/request?verb=GetRecord&metadataPrefix=oai_dc&identifier=oai:dspace6:nls/27837
>
> returns
> So that first OAI returns the ID in the list and second it says "the ID
> does not exist". The second part I expected because I want to exclude all
> items under this community. But the first part - the non empty list of IDs
> was unexpected.
>
> Is there an explanation of this or is this a defect in OAI?
>
>
>
--
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] Strange behaviour of OAI in 6.2
May be it works the same in older versions too. I have not checked.
I want to exclude from OAI the items under two collections and one
community.
I have in xoai.xml filter and condition:
org.dspace.xoai.filter.ColComFilter
col_nls_87
col_nls_25523
com_nls_22332
and the main part of ColComFilter.java is:
public boolean isShown(DSpaceItem item) {
if (collectionSpecs == null) {
getCollectionSpecs();
}
for (ReferenceSet rs : item.getSets()) {
if (collectionSpecs.contains(rs.getSetSpec())) {
return true;
}
}
return false;
}
This works fine for the two collections:
http://dspace6:8080/oai/request?verb=ListIdentifiers&metadataPrefix=oai_dc&set=col_nls_87
http://dspace6:8080/oai/request?verb=ListIdentifiers&metadataPrefix=oai_dc&set=col_nls_25523
return http://dspace6:8080/oai/request?verb=ListIdentifiers&metadataPrefix=oai_dc&set=com_nls_22332
returns a lot of identifiers:
completeListSize="3731" (which is the size of the community)
and many entries like:
oai:dspace6:nls/27837
2017-12-14T09:52:31Z
com_nls_22332
com_nls_94
col_nls_26938
But for everyone of the identifiers in the list (I tried 20) the request
http://dspace6:8080/oai/request?verb=GetRecord&metadataPrefix=oai_dc&identifier=oai:dspace6:nls/27837
returns https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
Re: [dspace-tech] Schibboleth in DSpace
Hi John, Since it sounds like you've activated *both* Password and Shibboleth authentication, then you will see a page that asks you which authentication method you wish to use. That's normal behavior. That page is only skipped over if you have a single authentication plugin enabled. As for DSpace + Shibboleth, DSpace does not autoconfigure your Shibboleth backend. You will need to configure the Shibboleth connection info in the [dspace]/config/modules/authentication-shibboleth.cfg file. Much more info on that is in the Shibboleth Plugin docs at https://wiki.duraspace.org/display/DSDOC5x/Authentication+Plugins#AuthenticationPlugins-ShibbolethAuthentication To answer your other questions, I think most of that information can be found in the "Configuration Shibboleth Authentication" section here: section: https://wiki.duraspace.org/display/DSDOC5x/Authentication+Plugins#AuthenticationPlugins-ConfiguringShibbolethAuthentication Regarding the IdP question, here's a key point from the documentation: "In the Shibboleth terminology DSpace is a Service Provider which receives authentication information and then based upon that provides a service to the user. To use Shibboleth, DSpace *requires *that you use Apache installed with the mod_shib module acting as a proxy for all HTTP requests for your servlet container (typically Tomcat). DSpace will receive authentication information from the mod_shib module through HTTP headers." Hopefully that'll help clarify things. Let us know if you have further questions. Tim On Thu, Mar 15, 2018 at 5:50 AM John Milano wrote: > Hi Everybody, > > I am using Dspace 5 and trying to use Schibboleth authentication on it. > > I have configured Shibd and apache on Ubuntu and activated the Plugin in > the authentication configuration file. > > Result: An extra page has appeared with two authentication methods, > password login is working like before, but Shibboleth login page is empty. > > My question: Does DSpace provide a frontend layout with the IdP list in it > for Shibboleth or should I use the Javascript files which Shibboleth > provoides > in order to implement it? And if so where can I include the javascripts so > that the IdP list appears on this page? > > -- > 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. > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- 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] BUILD FAILED /build/dspace-6.0
hi. I'm having problems installing DSpace 6. when I type: ant fresh_install I receive this ERROR MESSAGE BUILD FAILED /build/dspace-6.0-src-release/dspace/target/dspace-installer/build.xml:792: Java returned: 1 more details: root@dspace-CLUB:/build/dspace-6.0-src-release/dspace/target/dspace-installer# ant fresh_install Buildfile: /build/dspace-6.0-src-release/dspace/target/dspace-installer/build.xml init_installation: prepare_configs: [mkdir] Created dir: /build/dspace-6.0-src-release/dspace/target/dspace-installer/config-temp [copy] Copying 156 files to /build/dspace-6.0-src-release/dspace/target/dspace-installer/config-temp [copy] Copying 1 file to /build/dspace-6.0-src-release/dspace/target/dspace-installer/config-temp [copy] Copying 16 files to /build/dspace-6.0-src-release/dspace/target/dspace-installer/config-temp init_configs: [copy] Copying 1 file to /dspace/config [delete] Deleting directory /build/dspace-6.0-src-release/dspace/target/dspace-installer/config-temp test_database: [java] 2018-03-15 17:40:44,731 WARN org.apache.commons.configuration.DefaultConfigurationBuilder @ Internal error [java] org.apache.commons.configuration.ConfigurationException: Cannot locate configuration source local.cfg [java] at org.apache.commons.configuration.AbstractFileConfiguration.load(AbstractFileConfiguration.java:259) [java] at org.apache.commons.configuration.AbstractFileConfiguration.load(AbstractFileConfiguration.java:238) [java] at org.apache.commons.configuration.DefaultConfigurationBuilder$FileConfigurationProvider.getConfiguration(DefaultConfigurationBuilder.java:1455) [java] at org.apache.commons.configuration.DefaultConfigurationBuilder$ConfigurationBeanFactory.createBean(DefaultConfigurationBuilder.java:1321) [java] at org.apache.commons.configuration.beanutils.BeanHelper.createBean(BeanHelper.java:390) [java] at org.apache.commons.configuration.beanutils.BeanHelper.createBean(BeanHelper.java:412) [java] at org.apache.commons.configuration.beanutils.BeanHelper.createBean(BeanHelper.java:426) [java] at org.apache.commons.configuration.DefaultConfigurationBuilder.createConfigurationAt(DefaultConfigurationBuilder.java:855) [java] at org.apache.commons.configuration.DefaultConfigurationBuilder.initCombinedConfiguration(DefaultConfigurationBuilder.java:719) [java] at org.apache.commons.configuration.DefaultConfigurationBuilder.getConfiguration(DefaultConfigurationBuilder.java:622) [java] at org.apache.commons.configuration.DefaultConfigurationBuilder.getConfiguration(DefaultConfigurationBuilder.java:587) [java] at org.dspace.servicemanager.config.DSpaceConfigurationService.loadInitialConfig(DSpaceConfigurationService.java:494) [java] at org.dspace.servicemanager.config.DSpaceConfigurationService.(DSpaceConfigurationService.java:87) [java] at org.dspace.servicemanager.DSpaceKernelImpl.start(DSpaceKernelImpl.java:148) [java] at org.dspace.servicemanager.DSpaceKernelImpl.start(DSpaceKernelImpl.java:128) [java] at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:49) [java] 2018-03-15 17:40:52,311 WARN org.dspace.services.email.EmailServiceImpl @ Couldn't get an email session from environment: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial [java] 2018-03-15 17:40:53,614 ERROR org.dspace.storage.rdbms.DatabaseUtils @ Unable to setup Flyway against DSpace database [java] java.sql.SQLException: Cannot create PoolableConnectionFactory (FATAL: password authentication failed for user "dspace") [java] at org.apache.commons.dbcp2.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:2294) [java] at org.apache.commons.dbcp2.BasicDataSource.createDataSource(BasicDataSource.java:2039) [java] at org.apache.commons.dbcp2.BasicDataSource.getConnection(BasicDataSource.java:1533) [java] at org.dspace.storage.rdbms.DatabaseUtils.setupFlyway(DatabaseUtils.java:473) [java] at org.dspace.storage.rdbms.DatabaseUtils.main(DatabaseUtils.java:98) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [java] at java.lang.reflect.Method.invoke(Method.java:606) [java] at org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229) [java] at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81) [java] Caused by: org.postgresql.util.PSQLException: FATAL: password authentication failed for user "dspace" [java] at org
[dspace-tech] Add the link of a publication type to the navigation bar
Hello everybody I have added other publication type more to my Dspace-Cris, the publication type is thesis, and i would like to add "thesis" link to navigation bar. But i don´t found how to do it. Any suggestions Regards Gonzalo -- 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] Apache mod-proxy
Can anybody shed some light on what the following lines from my apache.log indicate: 54.37.81.59 - - [15/Mar/2018:14:02:10 +0200] "CONNECT www.google.com:443 HTTP/1.1" 200 44921 "-" "Mozilla/5.0 (Windows NT 6.2; rv:55.0) Gecko/20100101 Firefox/55.0" 54.37.81.59 - - [15/Mar/2018:14:02:17 +0200] "CONNECT www.google.com:443 HTTP/1.1" 200 44921 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36" 54.37.81.59 - - [15/Mar/2018:14:02:18 +0200] "CONNECT www.google.com:443 HTTP/1.1" 200 44921 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063" Am I correct in thinking that this means someone is using my proxy server to connect to google? I don't understand how this could be since I have ProxyRequests Off in proxy.conf. So it should only act as a reverse proxy, or have I completely misunderstood everything? Sorry, I realise this is only indirectly related to DSpace, but I am using Apache and mod_proxy in front of my tomcat, as I believe others on this list are also doing. Apache 2.4.18 Sean -- -- 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] Schibboleth in DSpace
Hi Everybody, I am using Dspace 5 and trying to use Schibboleth authentication on it. I have configured Shibd and apache on Ubuntu and activated the Plugin in the authentication configuration file. Result: An extra page has appeared with two authentication methods, password login is working like before, but Shibboleth login page is empty. My question: Does DSpace provide a frontend layout with the IdP list in it for Shibboleth or should I use the Javascript files which Shibboleth provoides in order to implement it? And if so where can I include the javascripts so that the IdP list appears on this page? -- 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] It is possible not to show "dc.format.extent" at OAI?
Hi Claudia, Yes, it helped me a lot. All is working now. Thank you very much. El dijous, 15 març de 2018 10:16:26 UTC+1, Claudia Jürgen va escriure: > > Hello Mariangels, > > assuming you are referring to the default oai_dc OAI/PMH metadata format > you can adjust it here: > > https://github.com/DSpace/DSpace/blob/dspace-5.5/dspace/config/crosswalks/oai/metadataFormats/oai_dc.xsl#L114 > > > Hope this helps > > Claudia Jürgen > > > Am 15.03.2018 um 10:11 schrieb Mariangels: > > Hello, > > > > We are working with DSpace 5.5 and xmlui. > > We have a problem: > > > > In our repositoy we have this kind of metadata for all our records: > > > > Example: > > > > dc.format = application/pdf > > dc.format.extent = 234 p. > > > > At our OAI screen we can see: > > > > application/pdf > > 214 p. > > > > We would like our OAI just shows the metadata dc.format and *NOT * > > dc.format.extent > > > > application/pdf > > > > How can I get this? What I need to change? > > > > Thanks in advance. > > > > > > > > > > > > > > > > > > -- > 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 > 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] It is possible not to show "dc.format.extent" at OAI?
Hello Mariangels, assuming you are referring to the default oai_dc OAI/PMH metadata format you can adjust it here: https://github.com/DSpace/DSpace/blob/dspace-5.5/dspace/config/crosswalks/oai/metadataFormats/oai_dc.xsl#L114 Hope this helps Claudia Jürgen Am 15.03.2018 um 10:11 schrieb Mariangels: Hello, We are working with DSpace 5.5 and xmlui. We have a problem: In our repositoy we have this kind of metadata for all our records: Example: dc.format = application/pdf dc.format.extent = 234 p. At our OAI screen we can see: application/pdf 214 p. We would like our OAI just shows the metadata dc.format and *NOT * dc.format.extent application/pdf How can I get this? What I need to change? Thanks in advance. -- 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.
[dspace-tech] It is possible not to show "dc.format.extent" at OAI?
Hello, We are working with DSpace 5.5 and xmlui. We have a problem: In our repositoy we have this kind of metadata for all our records: Example: dc.format = application/pdf dc.format.extent = 234 p. At our OAI screen we can see: application/pdf 214 p. We would like our OAI just shows the metadata dc.format and *NOT * dc.format.extent application/pdf How can I get this? What I need to change? Thanks in advance. -- 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] Traslate JSPUI
Hello, take a look at: https://wiki.duraspace.org/display/DSDOC6x/Localization+L10n#LocalizationL10n-JSPUIspecificlocalization Hope this helps Claudia Jürgen Am 15.03.2018 um 06:17 schrieb Rodrigo Sebastian Hidalgo Avila: Hello! I would like to know how I can translate the texts into Spanish from the jspui page of dspace. -- 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.
