Re: [dspace-tech] DSpaceMETSSIPProfile

2016-01-21 Thread Claudia Jürgen

Hallo Stefan,

there is a small error in your mets:

Thermodynamic Investigations in the Ternary Al-Ti-Cr
System


should be

Thermodynamic Investigations in the Ternary Al-Ti-Cr
System

"Info" with an upper case i.

Hope this helps

Claudia Jürgen



Am 21.01.2016 um 09:40 schrieb Stefan Fritzsche:

Dear Members,

when i start the the ingest with the packager command

dspace packager --eperson=foo@localhost -p 123456789/3 -t METS sip.zip

the packager terminates with the following message.

Ingesting package located at sip.zip
org.dspace.content.packager.PackageValidationException: Item cannot be
created without the required "title" DC metadata.
 at
org.dspace.content.packager.PackageUtils.checkItemMetadata(PackageUtils.java:135)
 at
org.dspace.content.packager.AbstractMETSIngester.ingestObject(AbstractMETSIngester.java:463)
 at
org.dspace.content.packager.AbstractMETSIngester.ingest(AbstractMETSIngester.java:228)
 at org.dspace.app.packager.Packager.ingest(Packager.java:570)
 at org.dspace.app.packager.Packager.main(Packager.java:427)
 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:497)
 at
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:226)
 at
org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:78)
org.dspace.content.packager.PackageValidationException: Item cannot be
created without the required "title" DC metadata.

I understand the error message but there is no DC requirements
documented at
https://wiki.duraspace.org/display/DSPACE/DSpaceMETSSIPProfile. Could
you point me what is wrong with the mets.xml. The testsystem use the out
of the box crosswalks and configurations.

Regards,
Stefan



--
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] Feed cache and sane defaults for webui.feed.cache.age

2016-01-21 Thread Alan Orth
Hi, DSpacers.

While waiting for some actions to happen based on our Atom and RSS feeds, I
was just noticing that both of them were nearly two days old, and both
contained different old items. On a hunch I cleared the Cocoon cache and
both were updated.

After some digging I found a few threads on the mailing list about both the
Cocoon cache and the `webui.feed.cache.age` setting, which defaults to
caching feeds for 48 hours(!). What is the relationship between the Cocoon
cache and the the feed cache? Is this a bug or did I just not wait long
enough to let DSpace update the cache?

Also, it seems like 48 hours is a bit high for a default, and more likely
to cause confusion than to save resources. Wouldn't a default closer to "a
few times a day"—perhaps 3, 4, 6, or 12 hours—make more sense? Surely we
can spare a few cycles every few hours to keep things fresh...?

Regards,
-- 
Alan Orth
alan.o...@gmail.com
https://englishbulgaria.net
https://alaninkenya.org
https://mjanja.ch

-- 
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] oai and access restricted items

2016-01-21 Thread Jose Blanco
Claudia.  I noticed that I was missing:
 DSpaceWithdrawnFilter.java
in dspace-oai/src/main/java/org/dspace/xoai/filter
so I copied the one from:
https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-oai/src/main/java/org/dspace/xoai/filter/DSpaceWithdrawnFilter.java

But now I see that all the other files in this directory are different from
the ones in this gihub repository.  I started off with 5.1 from a gz file.
I wonder what happened.  Should I just use all the files and directories
from the filter dir in github?

Thank you!
Jose

On Wed, Jan 20, 2016 at 5:15 PM, Jose Blanco  wrote:

> I have to go now but I think my problem is in the xoia.xml file.  I will
> change it tomorrow and see what happens.
>
> I'll let you know.
>
> -Jose
>
> On Wed, Jan 20, 2016 at 4:14 PM, Jose Blanco  wrote:
>
>> Claudia, I cant get to solr on the browser, put I put some debug
>> statements in the code and I can see that public is false for the item I'm
>> looking for as expected.
>>
>> 2016-01-20 16:01:35,475 INFO  org.dspace.xoai.app.XOAI @ Is Item Public
>> Jose = TEMP-BOGUS/236284 is false
>> 2016-01-20 16:01:35,477 INFO  org.dspace.xoai.app.XOAI @ OAI-Jose in
>> XOAI.java) processing handle = TEMP-BOGUS/236284
>> 2016-01-20 16:01:35,478 WARN  org.dspace.xoai.util.ItemUtils @
>> Authorization denied for action READ on BITSTREAM:563783 by user 0
>> org.dspace.authorize.AuthorizeException: Authorization denied for action
>> READ on BITSTREAM:563783 by user 0
>> at
>> org.dspace.authorize.AuthorizeManager.authorizeAction(AuthorizeManager.java:207)
>> at
>> org.dspace.authorize.AuthorizeManager.authorizeAction(AuthorizeManager.java:111)
>> at org.dspace.content.Bitstream.retrieve(Bitstream.java:604)
>> at org.dspace.xoai.util.ItemUtils.retrieveMetadata(ItemUtils.java:274)
>>
>> Where in the code does it check for public again? I'm using xoai.xml that
>> came with the 5.1 release. I have a feeling it's getting into solr with
>> public set to false, but that the code that retries it is ignoring the
>> setting.
>>
>> Thank you!
>> Jose
>>
>>
>> On Wed, Jan 20, 2016 at 8:55 AM, Claudia Jürgen <
>> claudia.juer...@tu-dortmund.de> wrote:
>>
>>> Hello Jose,
>>>
>>> you need not add this (unless you customized your xoai.xml and removed
>>> it or using another context). This is the default filter for the default
>>> context.
>>> Have you checked your oai solr data? The restricted item should have the
>>> field
>>> item.public set to false
>>>
>>>
>>> Claudia
>>>
>>>
>>>
>>> Am 19.01.2016 um 21:18 schrieb Jose Blanco:
>>>
 I just tried putting this:

  
  
  
  
  
  
  
  
  
  
  
  

 in xoai.xml

 but when I do oai/request?verb=Identify

 I get:

 2016-01-19 15:14:05,433 ERROR org.dspace.xoai.app.BasicConfiguration @
 Not
 able to start XOAI normal cache service.
 org.dspace.xoai.services.api.config.XOAIManagerResolverException:
 com.lyncode.xoai.dataprovider.exceptions.ConfigurationException:
 Unexpected
 element LeftCondition


 On Tue, Jan 19, 2016 at 4:04 AM, Claudia Jürgen <
 claudia.juer...@tu-dortmund.de> wrote:

 Hello Jose,
>
> I think the harvest.includedrestricted.oai dspace.cfg parameter is no
> longer valid since the xoai is in use.
> You can achieve it with xoai.xml setting. The default filter applied to
> the default context:
>
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>
> already contains an itemAccessCondition, which is based afair on the
> DEFAULT_ITEM_READ and not on the acutal rights.
>
> If you are using 5.1 and running
> [dspace]/bin/dspace oai import -c
> you might just be stuck with this error
> https://jira.duraspace.org/browse/DS-2543
> which was resolved in 5.3.
>
> Hope this helps
>
> Claudia Jürgen
>
>
>
>
> Am 18.01.2016 um 18:40 schrieb Jose Blanco:
>
> Going to re-post this question.
>>
>> -Jose
>>
>> On Wed, Jan 6, 2016 at 4:11 PM, Jose Blanco 
>> wrote:
>>
>> I tried it on 5.1.  I had an item that was completely restricted to a
>>
>>> group that was not Anonymous and I did:
>>>
>>> ./dspace oai -c import
>>>
>>> And the restricted item showed up.
>>>
>>> Do I need to make any changes to this file:
>>>
>>>
>>>
>>>
>>> 

[dspace-tech] DSPACE / tomcat hanging / Solr issue ?

2016-01-21 Thread Monika Mevenkamp
Looking at the output of jstack  I  see 7 blocks of 

"ajp-bio-8009-exec-224" daemon prio=10 tid=0x7f159c9ad000 nid=0x5076 
runnable [0x7f14a3343000]
   java.lang.Thread.State: RUNNABLE

….
at org.apache.solr.client.solrj.SolrServer.add(SolrServer.java:102)
at org.dspace.statistics.SolrLogger.postView(SolrLogger.java:229)
at 
org.dspace.statistics.SolrLoggerUsageEventListener.receiveEvent(SolrLoggerUsageEventListener.java:42)
at 
org.dspace.services.events.SystemEventService.fireLocalEvent(SystemEventService.java:144)
at 
org.dspace.services.events.SystemEventService.fireEvent(SystemEventService.java:86)
at 
org.dspace.app.webui.servlet.BitstreamServlet.doDSGet(BitstreamServlet.java:116)
at 
org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:130)
at 
org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:75)
...
at 
org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)

….


Theses are the only dspace related entries in the stack dump 

Looking at the Solr Admin UI I see 
JVM 35% full351.18 MB   of  989.88 MB
Physical Mem 95.8%  1.72GB  of  1.79GB   

The JVM args shown in the solr admin UI are 
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties
-Djava.io.tmpdir=/var/cache/tomcat/temp
-Djava.endorsed.dirs=
-Dcatalina.home=/usr/share/tomcat
-Dcatalina.base=/usr/share/tomcat
-Dfile.encoding=UTF-8
-XX:MaxPermSize=128M
-Xmx1024M
-Xms1024M

To give you a sense of the solr index; running a du -hm on the /dspace/solr dir 
I get 
du -s -hm  solr
3495solr
So that is about 5.5GB

The stats core has 3579463 docs 
The search core has 70372 docs

I am not sure what solr means with physical memory here 
I probably should increase it - but how ? 

Monika


 
Monika Mevenkamp
mo.me...@gmail.com

http://mo-meven.tumblr.com/
http://mcmprogramming.com/mo.meven/



-- 
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] oai and access restricted items

2016-01-21 Thread Claudia Jürgen

Hello Jose,

per default you can access solr only from the machine it's runnning on.

You can forward the graphical output in order to use a browser or access
it with command line tools like curl.
Here are som examples:
gives you the number of all items which are not public
curl -g http://localhost:8080/solr/oai/select -d
'q=item.public:false=0=xml'

gives you the complete information of single item
curl -g http://localhost:8080/solr/oai/select -d
'q=item.id:YOURITEMID=1=xml'

So check the data in the solr oai core. If it is not correct run a full
import.

[dspace]/bin/dspace oai import -c

[dspace]/bin/dspace oai import without -c is an incremental import and
will only add new items to the index, but does not reflect changes to
existing items.

and then clean your cache by running
[dspace]/bin/dspace oai clean-cache
or manually remove the data under
[dspace]/var/oai/requests

there was an issue https://jira.duraspace.org/browse/DS-2543 which was
resolved in 5.3 where running
[dspace]/bin/dspace oai import -c did not clear the cache

Hope this helps

Claudia

Am 20.01.2016 um 22:14 schrieb Jose Blanco:

Claudia, I cant get to solr on the browser, put I put some debug statements
in the code and I can see that public is false for the item I'm looking for
as expected.

2016-01-20 16:01:35,475 INFO  org.dspace.xoai.app.XOAI @ Is Item Public
Jose = TEMP-BOGUS/236284 is false
2016-01-20 16:01:35,477 INFO  org.dspace.xoai.app.XOAI @ OAI-Jose in
XOAI.java) processing handle = TEMP-BOGUS/236284
2016-01-20 16:01:35,478 WARN  org.dspace.xoai.util.ItemUtils @
Authorization denied for action READ on BITSTREAM:563783 by user 0
org.dspace.authorize.AuthorizeException: Authorization denied for action
READ on BITSTREAM:563783 by user 0
at
org.dspace.authorize.AuthorizeManager.authorizeAction(AuthorizeManager.java:207)
at
org.dspace.authorize.AuthorizeManager.authorizeAction(AuthorizeManager.java:111)
at org.dspace.content.Bitstream.retrieve(Bitstream.java:604)
at org.dspace.xoai.util.ItemUtils.retrieveMetadata(ItemUtils.java:274)

Where in the code does it check for public again? I'm using xoai.xml that
came with the 5.1 release. I have a feeling it's getting into solr with
public set to false, but that the code that retries it is ignoring the
setting.

Thank you!
Jose


On Wed, Jan 20, 2016 at 8:55 AM, Claudia Jürgen <
claudia.juer...@tu-dortmund.de> wrote:


Hello Jose,

you need not add this (unless you customized your xoai.xml and removed
it or using another context). This is the default filter for the default
context.
Have you checked your oai solr data? The restricted item should have the
field
item.public set to false


Claudia



Am 19.01.2016 um 21:18 schrieb Jose Blanco:


I just tried putting this:

  
  
  
  
  
  
  
  
  
  
  
  

in xoai.xml

but when I do oai/request?verb=Identify

I get:

2016-01-19 15:14:05,433 ERROR org.dspace.xoai.app.BasicConfiguration @ Not
able to start XOAI normal cache service.
org.dspace.xoai.services.api.config.XOAIManagerResolverException:
com.lyncode.xoai.dataprovider.exceptions.ConfigurationException:
Unexpected
element LeftCondition


On Tue, Jan 19, 2016 at 4:04 AM, Claudia Jürgen <
claudia.juer...@tu-dortmund.de> wrote:

Hello Jose,

I think the harvest.includedrestricted.oai dspace.cfg parameter is no
longer valid since the xoai is in use.
You can achieve it with xoai.xml setting. The default filter applied to
the default context:

  
  
  
  
  
  
  
  
  
  
  
  
  

already contains an itemAccessCondition, which is based afair on the
DEFAULT_ITEM_READ and not on the acutal rights.

If you are using 5.1 and running
[dspace]/bin/dspace oai import -c
you might just be stuck with this error
https://jira.duraspace.org/browse/DS-2543
which was resolved in 5.3.

Hope this helps

Claudia Jürgen




Am 18.01.2016 um 18:40 schrieb Jose Blanco:

Going to re-post this question.

-Jose

On Wed, Jan 6, 2016 at 4:11 PM, Jose Blanco  wrote:

I tried it on 5.1.  I had an item that was completely restricted to a


group that was not Anonymous and I did:

./dspace oai -c import

And the restricted item showed up.

Do I need to make any changes to this file:




https://github.com/DSpace/DSpace/blob/master/dspace/config/crosswalks/oai/xoai.xml#L51

Or should it just work by default.

Thank you!

On Thu, Dec 17, 2015 at 10:08 AM, helix84  wrote:

On Tue, Dec 15, 2015 at 5:10 PM, Jose Blanco 
wrote:


harvest.includerestricted.oai = false


I can't find where in the code it's used.

I couldn't find any uses, either.


We'll 

[dspace-tech] Need the complete java code to do bitstream updating/adding using the REST api

2016-01-21 Thread Tao Zhao
Hi all,

This is Tao Zhao from the University of Oklahoma Libraries. I'd really 
appreciate that if anybody has the java code that can update/add the item 
bitstream using the REST api on Dspace 5.x.

Thanks.

-- 
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] DSpace UI Prototype Challenge

2016-01-21 Thread Luiz dos Santos
Anybody knows something about the results of this challenge?

Best Regards
Luiz

-- 
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] DSpace UI Prototype Challenge

2016-01-21 Thread Tim Donohue

Hi Luiz,

Analysis of the prototypes is still ongoing (the goal is to have a final 
decision by sometime in mid-to-late March).


Currently, each of the prototype developers/teams is presenting their 
work to our DSpace UI Working Group & DSpace Committers (in recent weeks 
and coming weeks).  As each presentation occurs, we've been recording 
them and posting them for public viewing off the challenge wiki page at:


https://wiki.duraspace.org/display/DSPACE/DSpace+UI+Prototype+Challenge

Specifically they are here:
https://wiki.duraspace.org/display/DSPACE/DSpace+UI+Prototype+Challenge#DSpaceUIPrototypeChallenge-PrototypePresentationSchedule

We also have a public evaluation form available, where 
individuals/institutions can start to add their thoughts on prototypes. 
However, we haven't yet advertised this heavily on lists as the 
prototype presentations have not all occurred, and videos are not yet 
available.  Nonetheless, anyone can start to analyze and add opinions to 
this form. It's linked from:

https://wiki.duraspace.org/display/DSPACE/DSpace+UI+Prototype+Challenge#DSpaceUIPrototypeChallenge-PrototypeEvaluationProcess

- Tim

On 1/21/2016 11:53 AM, Luiz dos Santos wrote:

Anybody knows something about the results of this challenge?

Best Regards
Luiz
--
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



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

--
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] DSpace UI Prototype Challenge

2016-01-21 Thread Peter Dietz
Hi Luiz,

The prototypes are being presented each week in a webinar. There have been
3 sessions thus far. They are every Monday / Thursday at 10am (New York
time).
https://wiki.duraspace.org/display/DSPACE/DSpace+UI+Prototype+Challenge#DSpaceUIPrototypeChallenge-PrototypePresentationSchedule

The entries also have code and documentation available on that same wiki
page.



Peter Dietz
Longsight
www.longsight.com
pe...@longsight.com
p: 740-599-5005 x809

On Thu, Jan 21, 2016 at 12:53 PM, Luiz dos Santos  wrote:

> Anybody knows something about the results of this challenge?
>
> Best Regards
> Luiz
>
> --
> 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.
>

-- 
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] default.license not localized

2016-01-21 Thread Rafa Carreres
Hi, 

I am testing DSpace 5.4 with JSPUI. I've set three languages in the user 
interface (english, spanish and catalan). 

I have different versions of a number of files to accomplish the 
multilanguage issue: input-forms, messages.properties and others. 

They are working fine but, as for default.license I've found that this 
particular case is not working. 

Regardless the language in the selector, in the submission process, only 
the file default.license is showed. I mean, versions for spanish and 
catalan are ignored: default_es.license and default_ca.license. 

I've found that this is managed into the file 
[dspace-src]/dspace-api/src/main/java/org/dspace/core/LicenseManager.java, 
line 144: 

138 /** 
139  * Load in the default license. 
140  */ 
141 private static void init() 
142 { 
143 File licenseFile = new 
File(ConfigurationManager.getProperty("dspace.dir") 
144 + File.separator + "config" + File.separator + 
"default.license"); 
145 
146 FileInputStream  fir = null; 
147 InputStreamReader ir = null; 
148 BufferedReader br = null; 
149 try 
150 { 
151 
152 fir = new FileInputStream(licenseFile); 
153 ir = new InputStreamReader(fir, "UTF-8"); 
154 br = new BufferedReader(ir); 
155 String lineIn; 
156 LicenseManager.license = ""; 
157 
158 while ((lineIn = br.readLine()) != null) 
159 { 
160 LicenseManager.license = LicenseManager.license + 
lineIn + '\n'; 
161 } 
162 
163 br.close(); 
164 
165 } 
166 catch (IOException e) 
167 { 
168 log.error("Can't load license: " + licenseFile.toString() , 
e); 
169 
170 // FIXME: Maybe something more graceful here, but with the 
171 // configuration we can't do anything 
172 throw new IllegalStateException("Cannot load license: " 
173 + licenseFile.toString(),e); 
174 } 
175 finally 
176 { 
177 if (br != null) 
 

Am I right? Can anyone confirm this problem? 

Regards, 

-- 
__Rafael Carreres Paredes _ 
Programador - Subunidad de Sistemas 
Servicio de Informática - Universidad de Alicante 
   Alicante 03080   España 
Tel. 96 590 34 00 Ext.1174   Fax : 96 590 34 99 
mailto:r...@ua.es  
___ 

-- 
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] Blank metadatavalue(s) break item details layout

2016-01-21 Thread Feed My Lambs Esq.
I don't know how universal this is, but it was present in both of our 
DSpace versions (3.x / 5.5).

Through unknown mechanisms, a few handles were created (or augmented) with 
blank metadatavalue(s). While normally this resulted in rows with just a 
"description" without "content", in a few scenarios, the results were 
problematic for the item display / layout.

For a few days, I will leave the following record in this broken state or 
until someone else can confirm it:

http://cardinalscholar.bsu.edu/handle/123456789/199623
http://cardinalscholar.bsu.edu/handle/123456789/199623?show=full (to see 
the blank fields)

This result is that the div#ds-options-wrapper gets added to ds-body pushing 
it beneath the main item details rather than floating to the right on a normal 
item . This was 
caused by adding the blank value for the metadata field "dc.description". 
(with or without "language" populated)

Additionally, I found that if there is a secondary, blank URL record that 
is meant to be shown in the simple view (in our case 
dc.identifier.cardcat-url) that it turns much of the text on the page into 
a clickable link which is not the intended / desired behavior.

IMPORTANTLY -- removing the 2 empty metadata fields resolves both layout 
conditions. Both conditions occur independently of the other.

What I propose is that if the ingest / import / metadata edit forms aren't 
meant to weed out these items, then deleting blank fields out of the 
metadatavalue table could be added to a clean-up scheduled task or simply 
reject the creation of blank values in a metadatavalue record. I presume 
there could be legitimate uses for blank values but I haven't thought of 
any.

Or, (less desirably) make the simple item view more robust to handle empty 
values.

*Can someone intimately familiar with the metadatavalue table* say whether 
and when it is safe to *delete *values directly out of metadatavalue if the 
field_value is empty? Isn't deletion out of that table the only thing that 
happens on the administrative edit "Item metadata" page?
I noticed there are various differences to metadatavalue between versions 3 
and 5 so any recommendations on safe deletion may need affixed to a version 
number.

The DB diagram doesn't appear to leave any dangling (metadata_value_id) 
foreign keys around for deleted metadatavalue rows but I could be wrong.

-- 
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: Examples of extending/reusing Authority Control / ORCID

2016-01-21 Thread David Schuster
I would think the VIVO group would have some interest in this as well...???

On Thursday, January 21, 2016 at 1:41:58 PM UTC-6, Peter Dietz wrote:
>
> Hi All,
>
> The DSpace Authority framework currently has one implementation, ORCID. 
> And, the documentation for the Authority Framework, offers some guidance on 
> extending this, to build your own implementation to wire up other Authority 
> sources. I was wondering if anyone has done this yet, and had some lessons 
> learned?
>
>
> https://github.com/DSpace/DSpace/tree/master/dspace-api/src/main/java/org/dspace/authority
>
> Perhaps, this is loosely a follow up to my previous "nested metadata" 
> discussion. Though we don't need to support nested-metadata for this, just 
> a trustworthy source of data.
> https://groups.google.com/d/topic/dspace-tech/z7Nibc-3rJw/discussion
>
> At this moment, we don't plan on integrating with an existing data store, 
> but would be creating a data store from scratch, and then populating that 
> store from a local person provider (database, ldap, csv, ...). Then, 
> building an authority-service to use that new data store. It seems like a 
> lot of work, just for the purpose of having auto-complete for a given 
> metadata field.
>
> 
> Peter Dietz
> Longsight
> www.longsight.com
> pe...@longsight.com 
> p: 740-599-5005 x809
>

-- 
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] Examples of extending/reusing Authority Control / ORCID

2016-01-21 Thread Peter Dietz
Hi All,

The DSpace Authority framework currently has one implementation, ORCID.
And, the documentation for the Authority Framework, offers some guidance on
extending this, to build your own implementation to wire up other Authority
sources. I was wondering if anyone has done this yet, and had some lessons
learned?

https://github.com/DSpace/DSpace/tree/master/dspace-api/src/main/java/org/dspace/authority

Perhaps, this is loosely a follow up to my previous "nested metadata"
discussion. Though we don't need to support nested-metadata for this, just
a trustworthy source of data.
https://groups.google.com/d/topic/dspace-tech/z7Nibc-3rJw/discussion

At this moment, we don't plan on integrating with an existing data store,
but would be creating a data store from scratch, and then populating that
store from a local person provider (database, ldap, csv, ...). Then,
building an authority-service to use that new data store. It seems like a
lot of work, just for the purpose of having auto-complete for a given
metadata field.


Peter Dietz
Longsight
www.longsight.com
pe...@longsight.com
p: 740-599-5005 x809

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