date:20180413

Re: [dspace-tech] NullPointerException when visualizing an item

2018-04-13 Thread Gustavo Tonini

Thank you, Miika.
Worked around the problem by moving the item to the collection where it was 
supposed to be.

On Friday, April 13, 2018 at 3:10:32 PM UTC-3, Miika Nurminen wrote:
>
> On 10.4.2018 19:37, Gustavo Tonini wrote:
>
> Hello Tim, 
> thanks for your reply. The URL I mentioned before shows the Java stack 
> trace and Java full stack trace. I'm copying it below.
>
>
> Hello,
>
> if I read the code correctly, the NullPointerException seems to occur 
> while retrieving the handle of the parent DSpace object (i.e. the 
> collection that 123456789/77186 is supposed to be in) before generating the 
> Browse->This Collection links.
>
> Perhaps there is some problem in the database - either with connecting the 
> collection to item, or with the handle of the parent collection. 
>
>
> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-xmlui/src/main/java/org/dspace/app/xmlui/aspect/browseArtifacts/Navigation.java#L152
>
> java.lang.NullPointerException
>   at 
> org.dspace.app.xmlui.aspect.browseArtifacts.Navigation.addOptions(Navigation.java:152)
>   at 
> org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:239)
>   at sun.reflect.GeneratedMethodAccessor462.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
>   at com.sun.proxy.$Proxy255.startElement(Unknown Source)
>   at 
> org.apache.cocoon.environment.internal.EnvironmentChanger.startElement(EnvironmentStack.java:140)
>   at 
> org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87)
>   at 
> org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:94)
>   at 
> org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:251)
>   at sun.reflect.GeneratedMethodAccessor462.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
>   at com.sun.proxy.$Proxy255.startElement(Unknown Source)
>   at 
> org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:94)
>   at 
> org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:251)
>   at sun.reflect.GeneratedMethodAccessor462.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
>   at com.sun.proxy.$Proxy255.startElement(Unknown Source)
>   at 
> org.apache.cocoon.environment.internal.EnvironmentChanger.startElement(EnvironmentStack.java:140)
>   at 
> org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87)
>   at 
> org.apache.cocoon.components.sax.AbstractXMLByteStreamInterpreter.parse(AbstractXMLByteStreamInterpreter.java:117)
>   at 
> org.apache.cocoon.components.sax.XMLByteStreamInterpreter.deserialize(XMLByteStreamInterpreter.java:44)
>   at 
> org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.processXMLPipeline(AbstractCachingProcessingPipeline.java:324)
>   at 
> org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:750)
>   at sun.reflect.GeneratedMethodAccessor490.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
>   at com.sun.proxy.$Proxy242.process(Unknown Source)
>   at 
> org.apache.cocoon.components.source.impl.SitemapSource.toSAX(SitemapSource.java:362)
>   at 
> org.apache.cocoon.components.source.util.SourceUtil.toSAX(SourceUtil.java:111)
>   at 
> org.apache.cocoon.components.source.util.SourceUtil.parse(SourceUtil.java:294)
>   at 
> org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:136)
>   at sun.reflect.GeneratedMethodAccessor489.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
>   at com.sun.proxy.$Proxy243.generate(Unknown Source)
>   at 
>

[dspace-tech] Re: New field to form in JSPUI

2018-04-13 Thread Rodrigo Sebastian Hidalgo Avila

Can a new dublin core type be added to place the thesis approval grade?

-- 
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] Need to delete records on OAI

2018-04-13 Thread Aprendiz 2018

Hello Andrea, I have a problem with the DSPACE and the OAI-PHM, similar to 
the one of Demmis, it is not possible to update the records in the OAI 
../oai/request?verb=ListSets, It shows me the old configuration and old 
records (33) Now they are 97. As I show you the output of the command:
# curl 'http://localhost:8080/solr/oai/select?q=*:*=true=0'




  0
  0
  
*:*
true
0
  






A help please,
Thanks

El lunes, 8 de febrero de 2016, 23:15:17 (UTC-5), Andrea Schweer escribió:
>
> Hi,
>
> I'm really not sure what's going on. Your log shows DSpace posting 
> information to Solr, which is what I'd expect. Have you checked the 
> permissions of the Solr directory tree? It needs to be owned by the same 
> user that Tomcat runs under ([dspace]/solr/oai and subdirectories).
>
> As a last resort, you could manually delete everything from that solr 
> index, then run another import. It shouldn't really do anything different 
> compared to clean-cache, but you never know. 
>
> If you run eg
> curl 'http://localhost:8080/solr/oai/select?q=*:*=true=0'
> then you'll see how many items the OAI solr core currently knows about -- 
> look for numFound. numFound should be equal to the number of items (this 
> might include non-public items and deleted items) after running import.
>
> You can run
> curl --globoff http://localhost:8080/solr/oai/update -H "Content-Type: 
> text/xml" --data-binary '*:*'
> followed by
> curl --globoff 'http://localhost:8080/solr/oai/update?commit=true'
> to force-delete everything in that solr index (you might want to try this 
> on a test server first).
>
> numFound in the first query above should then be 0. Run clean-cache and 
> access your web interface *without* running the import command -- it too 
> should tell you that there are 0 identifiers. If it still claims that there 
> are items, you may have a web cache layer in front of your repository or 
> something? If you do get 0 identifiers via the web interface after the 
> delete, run the import command and check again. Hopefully you'll then see 
> exactly those items you're expecting to see.
>
> Just a very final comment -- what are you looking at in the OAI interface? 
> I just followed the links in your initial e-mail again and the OAI 
> interface now shows 30 records/identifiers, the same number of items as 
> shown in JSPUI. So perhaps your earlier steps actually did work and you're 
> just looking at an out-of-date web page for some reason?
>
> cheers,
> Andrea
>
> On 09/02/16 16:48, Demis Estabridis wrote:
>
> Hi Andrea, 
>
> Thanks again for your answer.
> I can confirm that we're using SOLR as database source for OAI.
>
> We run again the suggested commands and we had no errors on the logs but 
> no new result. Nothing changed. 
>
> /opt/dspace/bin/dspace oai clean-cache
> /opt/dspace/bin/dspace oai import –c
>
> Please, find here the logs with debug mode on.
> We did it with the tomcat user:
>
> 2016-02-08 22:24:29,115 INFO  org.dspace.core.ConfigurationManager @ 
> Loading from classloader: file:/opt/dspace/config/dspace.cfg
> 2016-02-08 22:24:29,148 INFO  org.dspace.core.ConfigurationManager @ Using 
> dspace provided log configuration (log.init.config)
> 2016-02-08 22:24:29,148 INFO  org.dspace.core.ConfigurationManager @ 
> Loading: /opt/dspace/config/log4j.properties
> 2016-02-08 22:24:33,149 DEBUG net.sf.ehcache.config.ConfigurationFactory @ 
> Configuring ehcache from InputStream
> 2016-02-08 22:24:33,271 DEBUG net.sf.ehcache.config.BeanHandler @ Ignoring 
> ehcache attribute xmlns:xsi
> 2016-02-08 22:24:33,271 DEBUG net.sf.ehcache.config.BeanHandler @ Ignoring 
> ehcache attribute xsi:noNamespaceSchemaLocation
> 2016-02-08 22:24:33,280 DEBUG net.sf.ehcache.config.DiskStoreConfiguration 
> @ Disk Store Path: /tmp
> 2016-02-08 22:24:33,306 DEBUG net.sf.ehcache.config.ConfigurationHelper @ 
> No CacheManagerEventListenerFactory class specified. Skipping...
> 2016-02-08 22:24:33,346 DEBUG net.sf.ehcache.config.ConfigurationHelper @ 
> No BootstrapCacheLoaderFactory class specified. Skipping...
> 2016-02-08 22:24:33,346 DEBUG net.sf.ehcache.config.ConfigurationHelper @ 
> No CacheExceptionHandlerFactory class specified. Skipping...
> 2016-02-08 22:24:35,926 INFO  org.dspace.storage.rdbms.DatabaseManager @ 
> DBMS is 'PostgreSQL'
> 2016-02-08 22:24:35,926 INFO  org.dspace.storage.rdbms.DatabaseManager @ 
> DBMS driver version is '9.4.5'
> 2016-02-08 22:24:35,966 INFO  org.dspace.storage.rdbms.DatabaseUtils @ 
> Loading Flyway DB migrations from: filesystem:/opt/dspace/etc/postgres, 
> classpath:org.dspace.storage.rdbms.sqlmigration.postgres, 
> classpath:org.dspace.storage.rdbms.migration
> 2016-02-08 22:24:35,999 INFO 
>  org.flywaydb.core.internal.dbsupport.DbSupportFactory @ Database: 
> jdbc:postgresql://localhost:5432/dspace (PostgreSQL 9.4)
> 2016-02-08 22:24:36,005 DEBUG org.flywaydb.core.Flyway @ DDL Transactions 
> Supported: true
> 2016-02-08 22:24:36,018 DEBUG org.flywaydb.core.Flyway @ Schema:

Re: [dspace-tech] NullPointerException when visualizing an item

2018-04-13 Thread Nurminen, Miika


On 10.4.2018 19:37, Gustavo Tonini wrote:

Hello Tim,
thanks for your reply. The URL I mentioned before shows the Java stack 
trace and Java full stack trace. I'm copying it below.




Hello,

if I read the code correctly, the NullPointerException seems to occur 
while retrieving the handle of the parent DSpace object (i.e. the 
collection that 123456789/77186 is supposed to be in) before generating 
the Browse->This Collection links.


Perhaps there is some problem in the database - either with connecting 
the collection to item, or with the handle of the parent collection.


https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-xmlui/src/main/java/org/dspace/app/xmlui/aspect/browseArtifacts/Navigation.java#L152


java.lang.NullPointerException
at 
org.dspace.app.xmlui.aspect.browseArtifacts.Navigation.addOptions(Navigation.java:152)
at 
org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:239)
at sun.reflect.GeneratedMethodAccessor462.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
at com.sun.proxy.$Proxy255.startElement(Unknown Source)
at 
org.apache.cocoon.environment.internal.EnvironmentChanger.startElement(EnvironmentStack.java:140)
at 
org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87)
at 
org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:94)
at 
org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:251)
at sun.reflect.GeneratedMethodAccessor462.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
at com.sun.proxy.$Proxy255.startElement(Unknown Source)
at 
org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:94)
at 
org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:251)
at sun.reflect.GeneratedMethodAccessor462.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
at com.sun.proxy.$Proxy255.startElement(Unknown Source)
at 
org.apache.cocoon.environment.internal.EnvironmentChanger.startElement(EnvironmentStack.java:140)
at 
org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87)
at 
org.apache.cocoon.components.sax.AbstractXMLByteStreamInterpreter.parse(AbstractXMLByteStreamInterpreter.java:117)
at 
org.apache.cocoon.components.sax.XMLByteStreamInterpreter.deserialize(XMLByteStreamInterpreter.java:44)
at 
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.processXMLPipeline(AbstractCachingProcessingPipeline.java:324)
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:750)
at sun.reflect.GeneratedMethodAccessor490.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
at com.sun.proxy.$Proxy242.process(Unknown Source)
at 
org.apache.cocoon.components.source.impl.SitemapSource.toSAX(SitemapSource.java:362)
at 
org.apache.cocoon.components.source.util.SourceUtil.toSAX(SourceUtil.java:111)
at 
org.apache.cocoon.components.source.util.SourceUtil.parse(SourceUtil.java:294)
at 
org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:136)
at sun.reflect.GeneratedMethodAccessor489.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
at com.sun.proxy.$Proxy243.generate(Unknown Source)
at 
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.processXMLPipeline(AbstractCachingProcessingPipeline.java:326)
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:750)
at

Re: [dspace-tech] Authentication error when depositing via SWORDv2

2018-04-13 Thread Tim Donohue

Hello Hrafn,

I've had a bit of time to dig on this today.  That "No plugin can
disseminate the requested formats" error seems to be the result of calling
a SWORDv2 path *without passing along an expected header*

So, for example, I can easily reproduce it via "curl", if I simply do a GET
against an existing item in the demo site.  (For this example, I'm using
this existing item: http://demo.dspace.org/xmlui/handle/10673/5 which has
an internal ID of "1fd633f5-5df9-4b50-b23f-bb1f951e57a4")

For example, this simple GET request will throw that "No plugin can
disseminate the requested formats" error:

curl -i -u dspacedemo+ad...@gmail.com:[password] -X GET
http://demo.dspace.org/swordv2/edit-media/1fd633f5-5df9-4b50-b23f-bb1f951e57a4

However, if I do the same GET request, but tell it I want "atom+xml"
format, then the request *succeeds* and I get back an ATOM response with
metadata about that Item

curl -i -H "Accept:application/atom+xml" -u
dspacedemo+ad...@gmail.com:[password]
-X GET
http://demo.dspace.org/swordv2/edit-media/1fd633f5-5df9-4b50-b23f-bb1f951e57a4

So, that error doesn't seem to be a bug, but instead is an improper call to
the "edit-media" path, as that path expects that you will pass along an
"Accept" header in your request. Based on the DSpace SWORDv2 disseminator
configuration, there are a limited number of valid "Accept" headers that
DSpace supports by default -- they are configured here:
https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/modules/swordv2-server.cfg#L254

My suspicion here is that some of your testing is passing this "Accept"
header along properly...while other scripts/tests may not be.  Either that,
or this "No plugin can disseminate the requested formats" error is not the
core problem you are encountering.  In which case, we may need more
examples of reproducing the core problem (ideally via "curl" commands, as
with "curl" it is much easier to see the headers/etc that are being passed
via the request).

Good luck,

- Tim

On Wed, Apr 11, 2018 at 8:27 AM MALMQUIST Hrafn 
wrote:

> Hello
>
>
> I'm just following up by adding that I replicate can the error on
> http://demo.dspace.org.
>
> Sending in a metadata only entry is mostly fine (see working.py). For the
> first few runs they went straight through but then an error was generated
> in the sword client but the deposited item materialised nonetheless (for
> instance: http://demo.dspace.org/xmlui/handle/10673/80)
>
>
> Example of an Edit-IRI
> http://demo.dspace.org/swordv2/edit/334112ee-077b-4192-9ba3-8606e399aa4d
>
> and the Edit-Media-IRI gives the same error:
>
>
> http://demo.dspace.org/swordv2/edit-media/334112ee-077b-4192-9ba3-8606e399aa4d
>
>
> To authenticate
>
> user: dspacedemo+ad...@gmail.com
>
> pass: dspace
>
>
> Any thoughts?
>
>
> Hrafn
> --
> *From:* dspace-tech@googlegroups.com  on
> behalf of MALMQUIST Hrafn 
> *Sent:* 11 April 2018 10:32:05
> *To:* tdono...@duraspace.org
>
> *Cc:* dspace-tech@googlegroups.com
> *Subject:* Re: [dspace-tech] Authentication error when depositing via
> SWORDv2
>
> Hello Tim
>
>
> Thank you for taking the time to reply and for good suggestions.
>
>
> The Edit-media error occurs before I hand over any data about whether or
> not I intend to deposit files (see attached simple-test.py). In this script
> I just hand over XML formatted metadata (entry variable) because this gives
> me the Edit-media IRI which is needed for me to deposit the files (in
> simple-test.py I am in fact reproducing the process on lines 252-268 on
> https://github.com/artefactual/archivematica-storage-service/blob/stable/0.11.x/storage_service/locations/models/dspace.py
>  with
> a view to make line 297 work).
>
> DSpace 6.2 log, at this point shows no error (see attached dspace.log)
>
>
> Python SWORDv2 Client log for the same process doesn't show an error
> either (see attached sword-client.log)
>
>
> So running the simple-test.py will result in an item being created in
> submissions DSpace with the declared metadata. It seems no error is logged.
>
>
> If the generated Edit-media IRI is opened, the "No plugin can disseminate
> the requested formats" error is displayed (which does not show up in logs).
> If I attempt to deposit files using this Edit-media IRI I get 403 errors
> which do show up in the SWORD client log as:
>
>
> DEBUG:urllib3.connectionpool:Starting new HTTP connection (1):
> test.digitalpreservation.is.ed.ac.uk
> DEBUG:urllib3.connectionpool:
> http://test.digitalpreservation.is.ed.ac.uk:80 "POST
> /swordv2/edit-media/a454b207-dea5-4fcb-ba80-1618317d10f0 HTTP/1.1" 403 996
>
> and in the DSpace log as:
>
> 2018-04-10 15:07:06,202 INFO  org.dspace.sword2.MediaResourceManagerDSpace
> @ hrafn.malmqu...@ed.ac.uk:session_id=0:replace_failed_authorisation:user=
> hrafn.malmqu...@ed.ac.uk,on_behalf_of=none
>
>
> Now, the fact that the curl command works and also a

Re: [dspace-tech] Re: Add messages in Spanish to JSPUI

2018-04-13 Thread Claudia Jürgen

Hi,

see
https://wiki.duraspace.org/display/DSDOC5x/Localization+L10n#LocalizationL10n-Localizationofinput-forms.xmlandlicense.default

Hope this helps

Claudia Jürgen

Am 12.04.2018 um 19:19 schrieb Rodrigo Sebastian Hidalgo Avila:

yes, I added the file messages_es, modified the language in dspace.cfg and
rebuilt dspace, but this form was not translated into Spanish.

El jueves, 12 de abril de 2018, 12:37:58 (UTC-4), gonzalo perl escribió:

After upload messages.propierties. You have to build dspace to translate
it. What is the form you are saying?

Regards
Gonzalo

El jue., 12 abr. 2018 16:18, Rodrigo Sebastian Hidalgo Avila <
rodrigo.m...@gmail.com > escribió:

Thank you very much for the information!
Now I get the dialogues in Spanish, but when I try to upload an item I
get the form in English, how can I change it to Spanish?

--
You received this message because you are subscribed to a topic in the
Google Groups "DSpace Technical Support" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/dspace-tech/e3e5TYcV4c8/unsubscribe.
To unsubscribe from this group and all its topics, 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.

--
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] New field to form in JSPUI

2018-04-13 Thread Claudia Jürgen

Hello,

see
https://wiki.duraspace.org/display/DSDOC5x/Submission+User+Interface#SubmissionUserInterface-CustomMetadata-entryPagesforSubmission

Hope this helps

Claudia Jürgen

Am 12.04.2018 um 16:51 schrieb Rodrigo Sebastian Hidalgo Avila:

How can I add a new field in the form to add an item to the collection in
JSPUI?

--
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

Re: [dspace-tech] NullPointerException when visualizing an item

[dspace-tech] Re: New field to form in JSPUI

Re: [dspace-tech] Need to delete records on OAI

Re: [dspace-tech] NullPointerException when visualizing an item

Re: [dspace-tech] Authentication error when depositing via SWORDv2

Re: [dspace-tech] Re: Add messages in Spanish to JSPUI

Re: [dspace-tech] New field to form in JSPUI

7 matches

Site Navigation

Mail list logo

Footer information