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  January 2006

JISC-REPOSITORIES January 2006

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Institutional Repositories: do they need a new name?

From:

"H.M. Gladney" <[log in to unmask]>

Reply-To:

H.M. Gladney

Date:

Thu, 19 Jan 2006 07:16:40 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (165 lines)

"ASK will build services on top of what is essentially an online file system
(VFS)"

That's the way mature content management systems have worked since they
first became widely used in the for-profit world over a decade ago.  See A
Storage Subsystem for Image and Records Management, IBM Systems Journal
32(3), 512-540, (1993).  See http://home.pacbell.net/hgladney/hmgpubs.htm
for more on the topic.

It seems to me that the academic world is about a decade behind the
for-profit world at designing and using content management technology.  BTW,
there exist about 80 open-source projects working on digital libraries
a.k.a. digital repositories a.k.a. digital content management a.k.a. ...
There are also more than a score of commercial offerings, with some of those
having no-fee versions.  See Borghoff, U. M., Rödig, P., Scheffczyk, J., &
Schmitz, L. 2003. Langzeitarchivierung: Methoden zur Erhaltung digitaler
Dokumente. Heidelberg: dpunkt.verlag. xv, 283 pp. ISBN 3-89864-245-3.  More
details from dpunkt.verlag Web site, retrieved February 24, 2004, from:
http://www.dpunkt.de/buch/3-89864-245-3.html  Much of this effort seems to
me terribly wasteful of skills that could be better applied.bb

These many projects all seem to work in isolation, notwithstanding
occasional pious lip-service about co-operation.  At least, many pubs and
web pages from this community seem singularly free of citations of other
people's work, and next to none of them.  See "Speculation about Faster
Progress towards Digital Repositories" in the Digital Document Quarterly at
http://home.pacbell.net/hgladney/ddq_4_4.htm#_Toc123007622.  

Best wishes,  Henry

H.M. Gladney, Ph.D.
   
-----Original Message-----
From: Repositories discussion list [mailto:[log in to unmask]]
On Behalf Of Alistair Young
Sent: Thursday, January 19, 2006 4:38 AM
To: [log in to unmask]
Subject: Re: Institutional Repositories: do they need a new name?

Hello everyone, thought I'd introduce myself to the list. I'm working on
Howard's ASK project and just getting to grips with the repo terminology.

I have a low-level interest in it all in that ASK will build services on top
of what is essentially an online file system (VFS).

I find it helpful to think of the VFS as being at the kernel level of a repo
system. It has levers and switches that the user layer can pull and press to
get at content in the repo. To do this, there's a layer between the user and
kernel layers which enforces access permissions on the levers and switches.

When a user's repo object tries to, say, read a file from the content store,
the access layer should obtain the user's "attribute" object and compare
what's in it with the rules governing access to the levers and switches
being accessed.

Which takes us up another layer to the authn/authz layer, where shibb
(guanxi yay!) lives.

The flow sort of goes, user presents themself at the repo front door.  
The repo says "go and get authenticated (shibb) and then come back here.".
User does so. Repo asks user's home institution for their attributes,
constructs a "digital badge" for the user, pins it to them and lets them in.
Various services within the repo only have to check the badge to determine
whether the user can use that service.

An interesting question at the moment is whether that badge should be
composed of IMS ES or SAML attributes.

thanks for listening!

Alistair


On 19 Jan 2006, at 11:53, rrankin wrote:

>  Is it a Collections Management System?
>
> Ricky
>
>
> __________________
> Ricky Rankin
> Principal Analyst
> Information Services
> Queen's University Belfast
>
> Tel: 02890 974824
> Fax: 02890 976586
> email: [log in to unmask]
>
>
> -----Original Message-----
> From: Repositories discussion list [mailto:JISC- 
> [log in to unmask]] On Behalf Of Phil Barker
> Sent: Thursday, January 19, 2006 10:39 AM
> To: [log in to unmask]
> Subject: Re: Institutional Repositories: do they need a new name?
>
> Hello Howard, everyone
> I think that Howard's "repository" might be a third sense of the word, 
> which you might expand as "repository system"
> (where a system is "A collection of components organized to accomplish 
> a specific function or set of functions"[1]). This would sit in 
> between the "repository service" as a putative component in the system 
> (though I guess Howard has called it Content management -- though it 
> wouldn't be a content management system) and "repository service" as 
> the service you provide to users once you have your "repository 
> system" and agreed on a whole load of explicit and implicit policies.
>
> As I understand it, work on reference models will help us understand 
> what the components of a "repository system" might be, and the work 
> done by other projects represented on this list (WM-Share, CD-LOR etc) 
> along with more general work on "repository ecologies" (Blinco and 
> McLean's Wheel of Fortune
> [2]) will help us understand the policies required to shape these 
> services.
> (NB, I'm not suggesting a decoupling of the two areas of work, it's 
> necessary that they feed into each other!)
>
> Phil
>
> [1] IEEE Std 610 : IEEE standard computer dictionary (1990) [2] here's 
> another version of the Wheel of Fortune:
> http://www.rubric.edu.au/extrafiles/wheel/index.html
>
> Howard Noble wrote:
>> Hello, like the postings on this subject.
>>
>> How about: a repository is an integrated set of software components 
>> that provide discrete services, examples of which are:
>>   a.. 2.1 Alert
>>   b.. 2.2 Archiving
>>   c.. 2.3 Authentication
>>   d.. 2.4 Authorisation
>>   e.. 2.5 Content management
>>   f.. 2.6 DRM
>>   g.. 2.7 Federated search
>>   h.. 2.8 Filing
>>   i.. 2.9 Group
>>   j.. 2.10 Harvesting
>>   k.. 2.11 Identifier
>>   l.. 2.12 Member
>>   m.. 2.13 Metadata management
>>   n.. 2.14 Packaging
>>   o.. 2.15 Person
>>   p.. 2.16 Rating/ annotation
>>   q.. 2.17 Resolver
>>   r.. 2.18 Role
>>   s.. 2.19 Search
>>   t.. 2.20 Service registry
>>   u.. 2.21 Workflow
>>   v.. 2.22 Accounting
>>   w.. 2.23 Version control
>>
>>
>>
>
> -- 
> Phil Barker                            Learning Technology Adviser
>       ICBL, School of Mathematical and Computer Sciences
>       Mountbatten Building, Heriot-Watt University,
>       Edinburgh, EH14 4AS
>       Tel: 0131 451 3278    Fax: 0131 451 3327
>       Web: http://www.icbl.hw.ac.uk/~philb/

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

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