date(DelegatingPreparedStatement.java:105)
[java] at
org.dspace.storage.rdbms.DatabaseManager.executeUpdate(Databa
seManager.java:1315)
[java] at
org.dspace.storage.rdbms.DatabaseManager.update(DatabaseManag
er.java:729)
[java] at
org.dspace.content.BitstreamFormat.update
*IF YOU HAVE ISSUES WITH ant fresh_install like the one below, JUST DELETE
YOUR DATABASES ON POSTGRES AND THE DSPACE FOLDER THEN START THE PROCEDURES
AFRESH... *
date(DelegatingPreparedStatement.java:105)
[java] at
org.dspace.storage.rdbms.DatabaseManager.executeUpdate(Databa
seManager.
On Thu, Jul 21, 2011 at 23:22, Stuart Lewis wrote:
> SWORD client (http://easydeposit.swordapp.org/)
Thanks, that looks like a very useful application.
Regards,
~~helix84
--
10 Tips for Better Web Security
Learn 10 ways
Hello,
We are in the process of making some final decisions regarding the
deployment of Dspace as the Digital Repository used by all primary and
secondary schools all around Greece.
On this point we would like to ask some critical questions concerning
the sustainability of a High Available
LinkedIn
Sandeep Bhavsar requested to add you as a connection on LinkedIn:
--
Terry,
I'd like to add you to my professional network on LinkedIn.
- Sandeep
Accept invitation from Sandeep Bhavsar
http://www.linkedin.com/e/-pn35zx-gqf
I'm curious: what is the problem here? Surely one still wants to
know how one came to have these items.
--
Mark H. Wood, Lead System Programmer mw...@iupui.edu
Asking whether markets are efficient is like asking whether people are smart.
pgpjS6W6eomlG.pgp
Description: PGP signature
Part of the point of XMLUI's design is that Aspects and Themes aren't
directly connected. Aspects put stuff into the DRI for any Theme to
use (or not) as it sees fit.
A Theme is selected by the URI path to the page to be composed. An
Aspect can leave hints upon which a Theme can base decisions,
On Fri, Jul 22, 2011 at 15:04, Mark H. Wood wrote:
> I'm curious: what is the problem here? Surely one still wants to
> know how one came to have these items.
I agree that traceability of submitters even after they left the
organization is a good thing. But let me explain one potential problem
Whenever someone says, "I want reports," I think: well, what you
*should* want is data that you can put into your favorite reporting
tools.
We have a little servlet that gives a snapshot of a handful of basic
overall metrics to slot into our "library dashboard". See DS-552 for
my approach. Some
Mark,
I'm working on trying to get tombstone behavior to work in the xmlui
environment. I have it working on in the jspui webapp.
So, I have successfully changed an aspect so that when an item is withdrawn a
pick list of 3 options ( reasons ) for withdrawing the items is presented to
the user
Hi, Mark, you are correct, this is what we wanted/needed. Thanks!
--
HARDY POTTINGER
University of Missouri Library Systems
http://lso.umsystem.edu/~pottingerhj/
"No matter how far down the wrong road you've gone,
turn back." --Turkish proverb
On 7/22/11 8:35 AM, "Mark H. Wood" wrote:
>Whe
Here at NASA, we have a "revalidation" process that requires us to determine on
a annual basis if a User still needs access to our repository. We have to have
some way to remove them if they don't. Perhaps a new column - something like
eperson_status - could be added to the EPerson table. So
Jose,
Storing the reason for the withdraw in the metadata is sensible for the
moment.
I'm not so sure you would need to create the second view/DSpaceObject type
to attain rendering the output of a tombstone page.
If a tombstone is put into place when the
Aha. There is a checkbox on the edit an eperson page that can be
unchecked to disallow log-ins. It could most likely be automated, if
it'd be a burden to do manually.
B--
>>> On 7/22/2011 at 9:21 AM, in message
<03de6124b1f32240b3692ed5e591ed162a2a1ef...@ndmsscc07.ndc.nasa.gov>,
"Thornton,
Susa
Susan:
What I am doing at Cornell University is taking inactive persons and unchecking
the "Can Log In" in dspace-admin/edit-epeople and putting "Inactive" in the
"Phone field. I can then search on them in the database using select * from
eperson where can_log_in='f' and phone='Inactive';
I
Sounds like a workable idea. Thanks George!
Sue
Sue Walker-Thornton
Software Developer/Database Administrator
NASA Langley Research Center|LITES Contract
(757) 224-4074
-Original Message-
From: George S Kozak [mailto:g...@cornell.edu]
Sent: Friday, July 22, 2011 12:45 PM
To: Thornton
Mark, I was kind of trying to do this. I started by creating an ItemViewerNew
( transformer ) using the esiting ItemViewer that was already there but
modifying as necessary to have the reason for withdraw show up on the short
display. According to what you are saying I should be able to create
On Fri, Jul 22, 2011 at 10:28 AM, Blanco, Jose wrote:
>
> Mark, I was kind of trying to do this. I started by creating an
> ItemViewerNew ( transformer ) using the esiting ItemViewer that was already
> there but modifying as necessary to have the reason for withdraw show up on
> the short disp
Alex Lemann's question of yesterday brought to mind a question that the group
might be able to help us with.
The process we are using to build content is that the library pre-populates
each faculty member's collection with citations, and we then ask faculty to
attach their pre-/post-print file
On Fri, Jul 22, 2011 at 03:27:55PM +0200, helix84 wrote:
> On Fri, Jul 22, 2011 at 15:04, Mark H. Wood wrote:
> > I'm curious: what is the problem here? Surely one still wants to
> > know how one came to have these items.
>
> I agree that traceability of submitters even after they left the
> or
On Fri, Jul 22, 2011 at 10:21:03AM -0500, Thornton, Susan M. (LARC-B702)[LITES]
wrote:
> Here at NASA, we have a "revalidation" process that requires us to
determine on a annual basis if a User still needs access to our
repository. We have to have some way to remove them if they don't.
That's wh
Mark, I think I understand your directions. Sorry if I'm being hard headed
about this, but I'm hoping that making this change will help me get smarter
about Manakin and Cocoon.
So, I created the selector. I think it does what is suppose to do.
I've changed the sitemap in the ArtifactBrowse as
On Fri, Jul 22, 2011 at 12:15 PM, Blanco, Jose wrote:
> Mark, I think I understand your directions. Sorry if I'm being hard headed
> about this, but I'm hoping that making this change will help me get smarter
> about Manakin and Cocoon.
Of course…
> So, I created the selector. I think it doe
Mark,
I have deployed these changes and when I get to a restricted item I just get a
page with no data:
( not sure if you can see this. If it ask you for username and password, I can
send it to you separately )
http://blancoj.dev.deepblue.lib.umich.edu/handle/TEMP-BOGUS/190931
This of course
Can anyone give me some insight to this error message? I find it weird that
the URL ends simply on "/browse". Not something like "/browse?type=author". I
can't see how a user would navigate to this URL aside from directly editing it.
I am currently running a 1.5.1 installation of Dspace. L
Hi Gregory,
There is probably nothing to worry about. Usually this particular error occurs
when a search engine spider is crawling your site. As well as following links,
some spiders (Yahoo slurp in particular I think) has a habit of trying out URLs
that aren't normally linked to, by strippin
26 matches
Mail list logo
