Hello *,
Sorry for taking this thread up again. As we at U.PORTO are also very
interested in the Federated Repository issue, due to our Organization
distribution.
Could some one tell if the proposal of Lerry Stone in the Dspace wiki:
http://wiki.dspace.org/index.php/ObjectUri
Is being
Sorry to take so long to reply but I got side tracked. One question.
On Thu, Feb 12, 2009 at 9:50 AM, Scott Phillips
scott.a.phill...@gmail.com wrote:
This patch will add:
Part A: The ability for a DSpace collection to be harvested from another
repository via OAI-PMH. When you look at the
On Thu, Mar 5, 2009 at 10:59 AM, Scott Phillips
scott.a.phill...@gmail.com wrote:
The OAI protocol handles resending items that have been updated since the
last harvest.
Could you expand on this a little for me as I am not very familiar
with the OAI protocol. If I import an item (meta data only)
John,
Down here in Texas we also face this challenge to create a federated
repository among all institutional repositories across the state. Up
until now we've been doing a manual federation process which includes
dspace imports and exports plus some scripts that work on those
exports.
Hi John,
you may use SRW/U to search. OAI-PMH is not made for searching, but for
harvesting.
Furthermore there is pf-DSpace for Federating DSpace see
http://hdl.handle.net/2160/281
But I don't know what has become of it.
Hope that helps
Claudia Jürgen
John Preston schrieb:
The individuals
Hi Claudia, Interesting scheme, but it requires more of a
relationship between the nodes than I require (or desire). The
federation that I'm thinking of is for searching. It would be nice for
any of the DSpace instances to auto magically discover who belongs to
the federation and should be
Hi John,
as SRW searches via the Lucene indexes, the fulltext (as keyword) will
be searched if it's extraction and indexing is done with filter-media.
Hope that helps
Claudia Jürgen
John Preston schrieb:
Hi Claudia, Interesting scheme, but it requires more of a
relationship between the
On Wed, Feb 11, 2009 at 07:19:06AM -0500, John Preston wrote:
The federation that I'm thinking of is for searching.
Note that this is a special case of the more general problem: my
institution or consortium operates a number of different digital
document repositories of various types, and I
to it.
Ralph
-Original Message-
From: Mark H. Wood [mailto:mw...@iupui.edu]
Sent: Wednesday, February 11, 2009 8:29 AM
To: dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Federating a number of DSpace instances
On Wed, Feb 11, 2009 at 07:19:06AM -0500, John Preston
It would be nice for any of the DSpace instances to auto magically
discover who belongs to the federation and should be searched.
Have each register itself in some sort of directory service. The
search front-end can then first search the directory to discover
participating repositories, or
We have that use case here, John -- we are implementing separate DSpace
instances for our 23 campuses, but we also need a separate interface that can
search them all.
We're just going to harvest the data using OAI-PMH. I'm sure you've thought of
that, too.
--Dave
==
David
We have a situation here in New Zealand where each University has a
repository (mainly dspace) and the National Library maintains an
OAI-powered search engine that runs across them.
OAI doesn't include the full text, so searching is significantly limited.
If you search for a relatively rare
Walker, David wrote:
We have that use case here, John -- we are implementing separate
DSpace instances for our 23 campuses, but we also need a separate
interface that can search them all.
NASA/Langley purchased Google to use as its internal search engine to
search only its internal
What you need probably depends on what you actually mean by and want from
federation.
If common search is your primary reason, and your content is largely open
access, you can set up a Google custom search engine that will only return
results from your DSpaces. This would just be regular Google
My use case involves running a number of DSpace instances in various
departments, and collaborating entities that hold digital materials
(text, image, video, spatial, etc). I need to have a central point for
users to search across all these instances. Some of the instances may
not be public.
The
On Tue, Feb 10, 2009 at 3:14 PM, John Preston byhisde...@gmail.com wrote:
My use case involves running a number of DSpace instances in various
departments, and collaborating entities that hold digital materials
(text, image, video, spatial, etc). I need to have a central point for
users to
The individuals departments will want to maintain their own instances
in some cases, thus I need to be able to search across them in these
cases.
John
On Tue, Feb 10, 2009 at 4:19 PM, Dorothea Salo ds...@library.wisc.edu wrote:
On Tue, Feb 10, 2009 at 3:14 PM, John Preston byhisde...@gmail.com
You can submit your sitemaps to yahoo and use their BOSS API to search
across multiple domains using
domain=dspace1.domain.tld,dspace2.domain.tld,dspace-n.domain.tld. I
believe yahoo is also working towards indexing dc meta data for the
semantic web, and hopefully they will integrate this into
18 matches
Mail list logo