JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for JISC-REPOSITORIES Archives


JISC-REPOSITORIES Archives

JISC-REPOSITORIES Archives


JISC-REPOSITORIES@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

JISC-REPOSITORIES Home

JISC-REPOSITORIES Home

JISC-REPOSITORIES  August 2006

JISC-REPOSITORIES August 2006

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Search Engine for Repositories Only?

From:

Sarah Taylor <[log in to unmask]>

Reply-To:

Sarah Taylor <[log in to unmask]>

Date:

Wed, 2 Aug 2006 16:11:59 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

"That might be the gist of it: There are those who think IRs are for

digital content management and preservation, and those who think IRs

are for maximizing research access-provision. It might be helpful to

distinguish OAI DL IRs (OAI-compliant Digital-Library IRs, for digital

content management and preservation) from OAI OA IRs (OAI-compliant

Open- Access IRs, for providing research access). What the requisite

search services and functionalities might be, and be for, may then look

quite different for the two kinds of IRs."



---



Please forgive me for what I am sure is a ludicrous question, but is there any particular reason why we can't think of an institutional repository - i.e. the same institutional repository - as being a mechanism for both preservation AND for maximising access to research? Why must we have one for one purpose and one for another? Surely these two intended functions of an IR can complement one another?



Sorry to address the list in such simplistic terms, but I've been following this debate with interest and just wanted some clarification.



Thanks,



Sarah



-------------------------------------------------------------

Sarah Taylor (née Kaufman)

Assistant Librarian

Electronic Services Development Team/e-space

Manchester Metropolitan University

Minshull House

47 - 49 Chorlton Street

Manchester

M1 3FY



[log in to unmask] 

http://www.mmu.ac.uk/library 

-----------------------------------------------------------



Before acting on this email or opening 

any attachments you should read the 

Manchester Metropolitan University's 

email disclaimer available on its website



http://www.mmu.ac.uk/emaildisclaimer 







>>> Stevan Harnad <[log in to unmask]> 02/08/2006 13:57:26 >>>

On Wed, 2 Aug 2006, Philip Hunter wrote:



> Stevan Harnad wrote:

> >

> > (2) Why build these national and local restricted range OAI search engines

> > instead of simply building restricted-range options into the

> > full-spectrum OAI search engines such as OAIster?

> > http://oaister.umdl.umich.edu/o/oaister/ 

> >

> There are a number of reasons why you might want national and restricted 

> range OAI search engines as part of a global infrastructure for repository 

> usage, including questions of quality assurance and the practical management 

> of repository networks. 



I don't understand. If you have T total local IRs harvested by a

full-spectrum OAI harvesting/searching service such as OAIster, and Q

of them meet your local or national quality standards, then why wouldn't

simply restricting to that Q subset of T be the local quality assurer?



And how do global or local OAI searcher/harvesters affect the practical

management of the local IRs themselves?



Or is it that there are specific search functionalities that the national or local

search engines would provide that global ones cannot or do not provide?



> This question came up at the WWW2006 JISC workshop 

> on repositories, where I suggested that global services might be built most 

> practically on the basis of locally developed and managed services. 



The rationale for the OAI protocol has been to develop global OAI services on top of

distributed local OAI data-providers (IRs) -- not on top of distributed local OAI 

services.



The latter is possible too, but I would be keen to know the concrete

functional objective of doing it that way.



> The institutional and geographic level levels of repository services which, 

> while of little or no interest to the user, offer a number features which 

> can support the quality and sustainability of global OAI search services.



I am not saying that there is no possible functional advantage there: I am just

saying I have not yet heard what it is, concretely. What are the institutional and

national OAI search engines meant to do that the global ones do not or cannot do?



> This is one of those quasi-theological issues which are often quite 

> divisive - do we work from the centre (full-spectrum OAI search engines, 

> harvesting local services directly,  with restricted range search options), 

> or do we build global services using a tiered structure (restricted range 

> OAI search engines whose aggregated records are globally harvested)?



It is only theological if we are not specific about exactly what concrete

functionality we have in mind. On the face of it, the OAI picture

is: distributed local OAI data-providers (IRs), plus global OAI

service-providers providing services on top of those local IRs. There

can of course be OAI services on top of OAI services too, but with

search-services in particular, it is not obvious what sorts of things

the subglobal ones would be doing that the global ones would/could not.



Please help me see!



> We might have to suck it and see. The choice also depends to some extent on 

> what the world at large thinks repositories are for - a matter clearly still 

> in flux.



That might be the gist of it: There are those who think IRs are for

digital content management and preservation, and those who think IRs

are for maximizing research access-provision. It might be helpful to

distinguish OAI DL IRs (OAI-compliant Digital-Library IRs, for digital

content management and preservation) from OAI OA IRs (OAI-compliant

Open- Access IRs, for providing research access). What the requisite

search services and functionalities might be, and be for, may then look

quite different for the two kinds of IRs.



(Very similar questions underlie the [what should likewise be functional

rather than theological] issues surrounding the question of central

versus local repositories: CRs vs. IRs. And again it depends on what

you want them for, and what you want them to do, how.)



(To go still further: In principle, the harvester of all harvesters is

google, and it harvests and inverts much of web content already. What

sets the OAI harvesters apart is that (1) they focus on a specific kind

of content, not all of webspace, and (2) they use the OAI tags. But of

course google could be restricted to that subset, and configured to allow

navigation based on the OAI tags too! Google Scholar is already going

in that direction. With a full-text harvester already trawling the net,

does OA/OAI really have to reduplicate the efforts? This is not a rhetorical

question, but a practical, functional one.)



Stevan Harnad

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
November 2005
October 2005


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager