Thank you for clarifying your earlier question.
As I now understand the question, you are asking how one might indicate that certain parts of a collection are not available for some form of public use- either within your institution or for loan to other institutions.
If this is your question, I would suggest that the element <userestrict> or <accessrestrict> would be the appropriate way to note such restrictions in EAD. The choice between them depends on whether the restriction is to physical access or to the further dissemination of information found in the materials.
Michael Fox
-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]]On Behalf Of Takahiro FUJIWARA
Sent: Thursday, January 13, 2005 12:10 AM
To: [log in to unmask]
Subject: access restrict or extended area
Hello Michael Fox and leading persons,
Thank you to reply me.
In my expression of public=EAD's external and closed=EAD's internal.
That's fine for me.
However, we need more status flags for the lending service of archives.
In my understanding, AUDIENCE="external" means the XML subtree which has
AUDIENCE="external" is able to display. And the XML subtree which has
AUDIENCE="internal" is not able to display. -- I think this is not described
as "not able to lend"
If there are no suitable element/attribute for lending service, then we want
to
use extended area. I'm sorry I don't know EAD in detail.
Do you know whether the EAD has the element for extended feature such as
lending service?
Takahiro Fujiwara
EAST Co., Ltd. Japan
----- Original Message -----
From: "Fox, Michael" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Wednesday, December 29, 2004 9:07 AM
Subject: Re: access restrict
As you say, "the usertype is managed by outside of the EAD". Unless you
are delivering raw XML and a stylesheet to your users (in which case none of
this coding means much as they can see the whole file), the tool that
generates the HTML you are delivering will be the place where this encoding
is processed and text is either displayed or suppressed.
If I understand your question correctly, you will use the AUDIENCE attribute
to control that processing. While this attribute has only two possible
values, external and internal, all your scenarios can be handled with these
two options.
Michael Fox
________________________________
From: Encoded Archival Description List on behalf of Takahiro FUJIWARA
Sent: Thu 12/23/2004 8:46 PM
To: [log in to unmask]
Subject: access restrict
Dear leading persons,
I am new to the list.
I'd like to know to use EAD element/attribute in case of following purpose.
We want to have 2 usertype and 3 status when display EAD listing or access
to the archives.
1. usertype=administrator
All EAD listing are displayed. And all status can be shown in order to
the maintenance.
2. usertype=public
a) The EAD description which has status="public" will be displayed
b) The EAD description which has status="description only" will be
displayed. But this user can not access to the archives by their hands.
Only all descriptions which has this status is able to read.
c) The EAD description which has status="closed" should not be displayed.
The usertype is managed by outside of the EAD.
How can I write that staus to EAD?
Takahiro Fujiwara
EAST Co., Ltd. Japan.
|