I'm currently running Dspace 1.3.2/Oracle/Solaris 9/on my production server.
I want to conduct an upgrade to 1.4.2. I successfully upgraded my test server
to 1.4.2. However, it contained a small amount of data and wasn't a really
valid test relative to the complex environment that has been built in
production. To conduct a valid test, I dropped entirely my Oracle database on
my test server, exported the production db into test, and then tarred and moved
/dspace_source and /dspace directories onto test. I've edited my dspace.cfg to
point to the test Oracle db and the test server, updated my wars and started
Tomcat and got in and conducted a couple of quick searches and then exited and
shutdown the Tomcat.
I have changed both the dspace.cfg handle number and the handle config.dct
files to represent my test server handle. How do I change the just the handle
prefix number associated with the entries. I've seen the entry regarding
migrating data from test to production entry on the wiki and isn't what I need.
Do I just need to modify all the prefix numbers in the Oracle db or is this
handle value stored elsewhere?
Thanks for any help.
Brian A. Helstien, SISD, MLS,
Director, Special Technologies Initiatives,
IDM, University Libraries x06913
University of Southern California, (213) 740-6913
Los Angeles, California, 90089 [EMAIL PROTECTED]
Information is independent of media or format
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Wednesday, October 24, 2007 12:00 PM
To: [email protected]
Subject: DSpace-tech Digest, Vol 18, Issue 35
Send DSpace-tech mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/dspace-tech
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific than "Re:
Contents of DSpace-tech digest..."
Today's Topics:
1. Re: Academic SRB support (MacKenzie Smith)
2. Re: Academic SRB support (Blanco, Jose)
3. Re: Academic SRB support (Cory Snavely)
4. Re: Academic SRB support (Richard Rodgers)
5. Re: Academic SRB support (Cory Snavely)
6. Re: Advanced search problems (Shane Beers)
----------------------------------------------------------------------
Message: 1
Date: Wed, 24 Oct 2007 10:37:04 -0400
From: MacKenzie Smith <[EMAIL PROTECTED]>
Subject: Re: [Dspace-tech] Academic SRB support
To: "Blanco, Jose" <[EMAIL PROTECTED]>
Cc: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi Jose,
I haven't gotten the official story from SDSC, but I do know that their
attention has shifted to iRODS as the next generation storage architecture for
long-term data management. iRODS will be 100% open source software (no more
dual license) which will be easier for the community to deal with.
My understanding is that the commercial (Nirvana) and non-commercial (plain
SRB) are actually the same thing... they just have dual license arrangement for
the codebase. So the API that Sun develops *should* also work for your plain
vanilla SRB instance too. You can verify that with the SDSC folks (or I can ask
them).
The DSpace work that we've done at MIT was for the old non-commercial SRB, and
we recently got the jargon client for iRODS, so those should be tested with the
1.4.x and 1.5 releases.
MacKenzie
> I wonder if any one has heard if the academic SRB ( non-commercial )
> is going to be discontinued? We have been discussing using a
> Honeycomb server for bit storage, and they have informed us that the
> academic SRB is going to be discontinued, so they are not interested
> in developing an API for it. They are working on developing a
> commercial Nirvana SRB API. I'm assuming that the configurable SRB
> coming out in a future release of Dspace is the academic?
>
> http://wiki.dspace.org/index.php/PluggableStorage ?
>
> Thank you!
> Jose
--
MacKenzie Smith
Associate Director for Technology
MIT Libraries
------------------------------
Message: 2
Date: Wed, 24 Oct 2007 10:46:36 -0400
From: "Blanco, Jose" <[EMAIL PROTECTED]>
Subject: Re: [Dspace-tech] Academic SRB support
To: "MacKenzie Smith" <[EMAIL PROTECTED]>
Cc: [email protected]
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
We just had a phone conference with Sun and the developer for the commercial
version of SRB at Nirvana ( Tino ) and were told that the commercial version of
SRB they have developed is not the same as the academic SRB. One thing they
have developed is file system based SRB which *should* work, and we are going
to try it out.
Thanks for this information!
Jose
-----Original Message-----
From: MacKenzie Smith [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 24, 2007 10:37 AM
To: Blanco, Jose
Cc: [email protected]
Subject: Re: [Dspace-tech] Academic SRB support
Hi Jose,
I haven't gotten the official story from SDSC, but I do know that their
attention has shifted to iRODS as the next generation storage architecture for
long-term data management. iRODS will be 100% open source software (no more
dual license) which will be easier for the community to deal with.
My understanding is that the commercial (Nirvana) and non-commercial (plain
SRB) are actually the same thing... they just have dual license arrangement for
the codebase. So the API that Sun develops *should* also work for your plain
vanilla SRB instance too. You can verify that with the SDSC folks (or I can ask
them).
The DSpace work that we've done at MIT was for the old non-commercial SRB, and
we recently got the jargon client for iRODS, so those should be tested with the
1.4.x and 1.5 releases.
MacKenzie
> I wonder if any one has heard if the academic SRB ( non-commercial )
> is going to be discontinued? We have been discussing using a
> Honeycomb server for bit storage, and they have informed us that the
> academic SRB is going to be discontinued, so they are not interested
> in developing an API for it. They are working on developing a
> commercial Nirvana SRB API. I'm assuming that the configurable SRB
> coming out in a future release of Dspace is the academic?
>
> http://wiki.dspace.org/index.php/PluggableStorage ?
>
> Thank you!
> Jose
--
MacKenzie Smith
Associate Director for Technology
MIT Libraries
------------------------------
Message: 3
Date: Wed, 24 Oct 2007 14:55:57 +0000
From: Cory Snavely <[EMAIL PROTECTED]>
Subject: Re: [Dspace-tech] Academic SRB support
To: "Blanco, Jose" <[EMAIL PROTECTED]>
Cc: MacKenzie Smith <[EMAIL PROTECTED]>,
[email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain
...and if it seems odd to anyone following this thread that the developers of
Nirvana SRB would suggest we achieve this integration by using the filesystem
emulation provided by Nirvana SRB, which in turn uses the Honeycomb API, know
that I definitely did point out that irony to them.
However, according to these developers, the Nirvana and SDSC SRB APIs differ
enough that that is the only way to do this without recoding the DSpace
bitstream storage manager.
Disappointing? Yeah.
So am I understanding correctly that in future versions of DSpace, support for
CAS systems and the like would be done in DSpace? I.e. we might expect there to
be direct Honeycomb, EMC Celera, iRODS, etc support right within DSpace? We're
trying to see the roadmap here.
c
On Wed, 2007-10-24 at 10:46 -0400, Blanco, Jose wrote:
> We just had a phone conference with Sun and the developer for the
> commercial version of SRB at Nirvana ( Tino ) and were told that the
> commercial version of SRB they have developed is not the same as the
> academic SRB. One thing they have developed is file system based SRB
> which *should* work, and we are going to try it out.
>
> Thanks for this information!
>
> Jose
>
> -----Original Message-----
> From: MacKenzie Smith [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 24, 2007 10:37 AM
> To: Blanco, Jose
> Cc: [email protected]
> Subject: Re: [Dspace-tech] Academic SRB support
>
> Hi Jose,
>
> I haven't gotten the official story from SDSC, but I do know that
> their attention has shifted to iRODS as the next generation storage
> architecture for long-term data management. iRODS will be 100% open
> source software (no more dual license) which will be easier for the
> community to deal with.
>
> My understanding is that the commercial (Nirvana) and non-commercial
> (plain SRB) are actually the same thing... they just have dual license
> arrangement for the codebase. So the API that Sun develops *should*
> also work for your plain vanilla SRB instance too. You can verify that
> with the SDSC folks (or I can ask them).
>
> The DSpace work that we've done at MIT was for the old non-commercial
> SRB, and we recently got the jargon client for iRODS, so those should
> be tested with the 1.4.x and 1.5 releases.
>
> MacKenzie
> > I wonder if any one has heard if the academic SRB ( non-commercial )
> > is going to be discontinued? We have been discussing using a
> > Honeycomb server for bit storage, and they have informed us that the
> > academic SRB is going to be discontinued, so they are not interested
> > in developing an API for it. They are working on developing a
> > commercial Nirvana SRB API. I'm assuming that the configurable SRB
> > coming out in a future release of Dspace is the academic?
> >
> > http://wiki.dspace.org/index.php/PluggableStorage ?
> >
> > Thank you!
> > Jose
>
>
> --
> MacKenzie Smith
> Associate Director for Technology
> MIT Libraries
>
>
> ----------------------------------------------------------------------
> --- This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
------------------------------
Message: 4
Date: Wed, 24 Oct 2007 11:19:00 -0400
From: Richard Rodgers <[EMAIL PROTECTED]>
Subject: Re: [Dspace-tech] Academic SRB support
To: Cory Snavely <[EMAIL PROTECTED]>
Cc: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain
Hi Cory:
See remarks below...
Thanks,
Richard
On Wed, 2007-10-24 at 14:55 +0000, Cory Snavely wrote:
> ...and if it seems odd to anyone following this thread that the
> developers of Nirvana SRB would suggest we achieve this integration by
> using the filesystem emulation provided by Nirvana SRB, which in turn
> uses the Honeycomb API, know that I definitely did point out that
> irony to them.
>
> However, according to these developers, the Nirvana and SDSC SRB APIs
> differ enough that that is the only way to do this without recoding
> the DSpace bitstream storage manager.
>
> Disappointing? Yeah.
>
> So am I understanding correctly that in future versions of DSpace,
> support for CAS systems and the like would be done in DSpace? I.e. we
> might expect there to be direct Honeycomb, EMC Celera, iRODS, etc
> support right within DSpace? We're trying to see the roadmap here.
The roadmap certainly embraces selectable back-end storage options.
There is a prototype pluggable storage abstraction at
http://wiki.dspace.org/index.php/PluggableStorage
that I hope will eventually make it's way into a release, and it's precise
purpose is to avoid the need to recode BitStreamStorage manager or any other
core code. It currently supports legacy DSpace filesystem, SRB, and Amazon S3,
and I've had some discussions with Honeycomb developers and I believe they are
attempting to write a DSpace implementation against that interface.
We are just now seeing enough options to generalize & abstract this layer, but
I am sure we will continue these efforts.
> c
>
> On Wed, 2007-10-24 at 10:46 -0400, Blanco, Jose wrote:
> > We just had a phone conference with Sun and the developer for the
> > commercial version of SRB at Nirvana ( Tino ) and were told that the
> > commercial version of SRB they have developed is not the same as the
> > academic SRB. One thing they have developed is file system based
> > SRB which *should* work, and we are going to try it out.
> >
> > Thanks for this information!
> >
> > Jose
> >
> > -----Original Message-----
> > From: MacKenzie Smith [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, October 24, 2007 10:37 AM
> > To: Blanco, Jose
> > Cc: [email protected]
> > Subject: Re: [Dspace-tech] Academic SRB support
> >
> > Hi Jose,
> >
> > I haven't gotten the official story from SDSC, but I do know that
> > their attention has shifted to iRODS as the next generation storage
> > architecture for long-term data management. iRODS will be 100% open
> > source software (no more dual license) which will be easier for the
> > community to deal with.
> >
> > My understanding is that the commercial (Nirvana) and non-commercial
> > (plain SRB) are actually the same thing... they just have dual
> > license arrangement for the codebase. So the API that Sun develops
> > *should* also work for your plain vanilla SRB instance too. You can
> > verify that with the SDSC folks (or I can ask them).
> >
> > The DSpace work that we've done at MIT was for the old
> > non-commercial SRB, and we recently got the jargon client for iRODS,
> > so those should be tested with the 1.4.x and 1.5 releases.
> >
> > MacKenzie
> > > I wonder if any one has heard if the academic SRB ( non-commercial
> > > ) is going to be discontinued? We have been discussing using a
> > > Honeycomb server for bit storage, and they have informed us that
> > > the academic SRB is going to be discontinued, so they are not
> > > interested in developing an API for it. They are working on
> > > developing a commercial Nirvana SRB API. I'm assuming that the
> > > configurable SRB coming out in a future release of Dspace is the academic?
> > >
> > > http://wiki.dspace.org/index.php/PluggableStorage ?
> > >
> > > Thank you!
> > > Jose
> >
> >
> > --
> > MacKenzie Smith
> > Associate Director for Technology
> > MIT Libraries
> >
> >
> > --------------------------------------------------------------------
> > ----- This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems? Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > DSpace-tech mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
> ----------------------------------------------------------------------
> --- This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
------------------------------
Message: 5
Date: Wed, 24 Oct 2007 15:46:30 +0000
From: Cory Snavely <[EMAIL PROTECTED]>
Subject: Re: [Dspace-tech] Academic SRB support
To: Richard Rodgers <[EMAIL PROTECTED]>
Cc: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain
Thanks. You say
> I've had some discussions with Honeycomb developers
Who are those folks?
On Wed, 2007-10-24 at 11:19 -0400, Richard Rodgers wrote:
> Hi Cory:
>
> See remarks below...
>
> Thanks,
>
> Richard
> On Wed, 2007-10-24 at 14:55 +0000, Cory Snavely wrote:
> > ...and if it seems odd to anyone following this thread that the
> > developers of Nirvana SRB would suggest we achieve this integration
> > by using the filesystem emulation provided by Nirvana SRB, which in
> > turn uses the Honeycomb API, know that I definitely did point out
> > that irony to them.
> >
> > However, according to these developers, the Nirvana and SDSC SRB
> > APIs differ enough that that is the only way to do this without
> > recoding the DSpace bitstream storage manager.
> >
> > Disappointing? Yeah.
> >
> > So am I understanding correctly that in future versions of DSpace,
> > support for CAS systems and the like would be done in DSpace? I.e.
> > we might expect there to be direct Honeycomb, EMC Celera, iRODS, etc
> > support right within DSpace? We're trying to see the roadmap here.
>
> The roadmap certainly embraces selectable back-end storage options.
> There is a prototype pluggable storage abstraction at
>
> http://wiki.dspace.org/index.php/PluggableStorage
>
> that I hope will eventually make it's way into a release, and it's
> precise purpose is to avoid the need to recode BitStreamStorage
> manager or any other core code. It currently supports legacy DSpace
> filesystem, SRB, and Amazon S3, and I've had some discussions with
> Honeycomb developers and I believe they are attempting to write a
> DSpace implementation against that interface.
>
> We are just now seeing enough options to generalize & abstract this
> layer, but I am sure we will continue these efforts.
>
> > c
> >
> > On Wed, 2007-10-24 at 10:46 -0400, Blanco, Jose wrote:
> > > We just had a phone conference with Sun and the developer for the
> > > commercial version of SRB at Nirvana ( Tino ) and were told that
> > > the commercial version of SRB they have developed is not the same
> > > as the academic SRB. One thing they have developed is file system
> > > based SRB which *should* work, and we are going to try it out.
> > >
> > > Thanks for this information!
> > >
> > > Jose
> > >
> > > -----Original Message-----
> > > From: MacKenzie Smith [mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, October 24, 2007 10:37 AM
> > > To: Blanco, Jose
> > > Cc: [email protected]
> > > Subject: Re: [Dspace-tech] Academic SRB support
> > >
> > > Hi Jose,
> > >
> > > I haven't gotten the official story from SDSC, but I do know that
> > > their attention has shifted to iRODS as the next generation
> > > storage architecture for long-term data management. iRODS will be
> > > 100% open source software (no more dual license) which will be
> > > easier for the community to deal with.
> > >
> > > My understanding is that the commercial (Nirvana) and
> > > non-commercial (plain SRB) are actually the same thing... they
> > > just have dual license arrangement for the codebase. So the API
> > > that Sun develops *should* also work for your plain vanilla SRB
> > > instance too. You can verify that with the SDSC folks (or I can ask them).
> > >
> > > The DSpace work that we've done at MIT was for the old
> > > non-commercial SRB, and we recently got the jargon client for
> > > iRODS, so those should be tested with the 1.4.x and 1.5 releases.
> > >
> > > MacKenzie
> > > > I wonder if any one has heard if the academic SRB (
> > > > non-commercial ) is going to be discontinued? We have been
> > > > discussing using a Honeycomb server for bit storage, and they
> > > > have informed us that the academic SRB is going to be
> > > > discontinued, so they are not interested in developing an API
> > > > for it. They are working on developing a commercial Nirvana SRB
> > > > API. I'm assuming that the configurable SRB coming out in a future
> > > > release of Dspace is the academic?
> > > >
> > > > http://wiki.dspace.org/index.php/PluggableStorage ?
> > > >
> > > > Thank you!
> > > > Jose
> > >
> > >
> > > --
> > > MacKenzie Smith
> > > Associate Director for Technology
> > > MIT Libraries
> > >
> > >
> > > ------------------------------------------------------------------
> > > ------- This SF.net email is sponsored by: Splunk Inc.
> > > Still grepping through log files to find problems? Stop.
> > > Now Search log events and configuration files using AJAX and a browser.
> > > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > > _______________________________________________
> > > DSpace-tech mailing list
> > > [email protected]
> > > https://lists.sourceforge.net/lists/listinfo/dspace-tech
> >
> > --------------------------------------------------------------------
> > ----- This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems? Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > DSpace-tech mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
------------------------------
Message: 6
Date: Wed, 24 Oct 2007 15:00:08 -0400
From: Shane Beers <[EMAIL PROTECTED]>
Subject: Re: [Dspace-tech] Advanced search problems
To: Tim Donohue <[EMAIL PROTECTED]>
Cc: dspace-tech <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
So, after a bunch of testing on our end, I can pretty much decidedly say "I
have no idea what's going on."
Every night at 3:00am or so our server reboots, and following this reboot our
nightly scripts run. They have typically run filter-media, index-all, and the
subscription mailings. We have tested removing the filter-media section of the
nightly script and running the index-all as root during the script, in case
there was some permissions error taking place.
I ran Luke on our server and checked out the index. Interestingly, the etd_disc
index was not available to search against. When I manually ran (as root)
index-all in the dspace/bin directory and reloaded the index in Luke, etd_disc
was now there.
What I don't understand is that the index is clearly being re-written every
night, but the etd_disc index is not being created. This makes no sense,
because the nightly script just runs the same index-all that I run manually.
Any ideas?
Shane Beers
Digital Repository Services Librarian
George Mason University
[EMAIL PROTECTED]
703-993-3742
On Oct 15, 2007, at 10:40 AM, Tim Donohue wrote:
> Shane,
>
> That is odd...
>
> Have you double-checked all your log files, to make sure you're not
> getting any errors underneath after performing a search? So,
> checking the [dspace]/log/dspace.log and your Tomcat log file (e.g.
> [tomcat]/logs/catalina.out)
>
> If there's nothing strange in the log files after a search, you may
> also want to rerun your 'index-all', and check the logs after re-
> indexing (to make sure the indexer isn't running into strange issues).
>
> If nothing strange is happening in your logs, the next step you could
> take is to see what Lucene (underlying DSpace search engine) is
> actually indexing underneath. A good tool for this is Luke
> (http://www.getopt.org/luke/). You can point Luke at your [dspace]/
> search/ directory (where the DSpace Lucene Index is), and it will tell
> you all the documents you have indexed, and let you perform some basic
> browsing or searches directly against Lucene.
>
> However, I will admit, Luke does not have the *easiest* interface to
> understand. You'd mostly want to look at the "Documents" tab, to see
> all the documents Lucene indexed, and see if you can browse- by your
> custom field.
>
> Hopefully this gives you a few more things to look at. Let us know if
> you figure out what is going on!
>
> - Tim
>
> Shane Beers wrote:
>> Unfortunately (or perhaps fortunately, as I would feel pretty dumb if
>> that was the problem) that was just a typo on my own part in the
>> email - not in dspace.cfg I'm still at a loss...
>> Shane Beers
>> Digital Repository Services Librarian George Mason University
>> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>> 703-993-3742
>> On Oct 12, 2007, at 3:23 AM, Claudia J?rgen wrote:
>>> Hi Shane,
>>>
>>> if this is a cut'n paste of your changes you simply got a typo
>>> there,
>>> > search.index.13 = edt_disc:thesis.degree.discipline
>>>
>>> should be
>>> search.index.13 = etd_disc:thesis.degree.discipline
>>>
>>> sunny greetings
>>>
>>> Claudia
>>>
>>>
>>> Shane Beers schrieb:
>>>> I am having issues with my search results when using the advanced
>>>> search in our archive. I have added the "thesis"
>>>> metadata schema to handle ETD documents, and these documents work
>>>> great normally. I have edited the dspace.cfg to add:
>>>> search.index.13 = edt_disc:thesis.degree.discipline Following that,
>>>> I edited the advanced.jsp in <dspace-source> to add the appropriate
>>>> element, with the following section in each of the three search box
>>>> areas:
>>>> <option value="etd_disc" <%= field1.equals("etd_disc") ?
>>>> "selected=\"selected\"\"" : "" %>><fmt:message
>>>> key="jsp.search.advanced.type.etd_disc"/></option>
>>>> And then added in the appropriate element in Messages.properties,
>>>> rebuilt, reindexed and all that.
>>>> The field appears correctly, but when searching for terms that I
>>>> know are there, I get no results. Additionally, a strange thing
>>>> happens when no results are found that does not happen with any
>>>> other search field - all 3 search boxes switch to "Degree
>>>> Discipline" (the term I used in Messages.properties). This is just
>>>> something I noticed that may help in a diagnosis.
>>>> I'm not certain if I'm missing something or not, but I would really
>>>> like this search index to function correctly.
>>>> Shane Beers
>>>> Digital Repository Services Librarian George Mason University
>>>> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>>>> 703-993-3742
>>>> -------------------------------------------------------------------
>>>> -----
>>>> -------------------------------------------------------------------
>>>> ------
>>>> This SF.net email is sponsored by: Splunk Inc.
>>>> Still grepping through log files to find problems? Stop.
>>>> Now Search log events and configuration files using AJAX and a
>>>> browser.
>>>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>>>> -------------------------------------------------------------------
>>>> -----
>>>> _______________________________________________
>>>> DSpace-tech mailing list
>>>> [email protected] <mailto:DSpace-
>>>> [EMAIL PROTECTED]>
>>>> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>> ---------------------------------------------------------------------
>> ---
>> ---------------------------------------------------------------------
>> ----
>> This SF.net email is sponsored by: Splunk Inc.
>> Still grepping through log files to find problems? Stop.
>> Now Search log events and configuration files using AJAX and a
>> browser.
>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>> ---------------------------------------------------------------------
>> ---
>> _______________________________________________
>> DSpace-tech mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
> --
>
> ========================================
> Tim Donohue
> Research Programmer, Illinois Digital Environment for Access to
> Learning and Scholarship (IDEALS)
> 135 Grainger Engineering Library
> University of Illinois at Urbana-Champaign
>
> email: [EMAIL PROTECTED]
> web: http://www.ideals.uiuc.edu
> phone: (217) 333-4648
> fax: (217) 244-7764
> ========================================
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
------------------------------
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
End of DSpace-tech Digest, Vol 18, Issue 35
*******************************************
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
