LISTSERV mailing list manager LISTSERV 16.5

Help for NDSA-CONTENT Archives


NDSA-CONTENT Archives

NDSA-CONTENT Archives


NDSA-CONTENT@LISTS.CLIR.ORG


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

NDSA-CONTENT Home

NDSA-CONTENT Home

NDSA-CONTENT  July 2011, Week 2

NDSA-CONTENT July 2011, Week 2

Subject:

Re: Please comment or respond by 7/22: Content Registry Fields

From:

John Weise <[log in to unmask]>

Reply-To:

The NDSA Content working group list <[log in to unmask]>

Date:

Mon, 11 Jul 2011 17:45:35 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (197 lines)

I am not sure I know, Abbie, what you mean by "overall".  Availability of
content within a collection is sometimes mixed. Should the field support
multiple values? Or perhaps, if any portion of it is "open" the value should
be "online"? There are also collections which are online, but restricted to
use by members of a specific user community (e.g., a university), and yet
not limited to a specific site.And then there are collections where online
access is in part determined by the geographic location of the user. I'm
sure there are other divisions, as well as the danger of splitting hairs.
What again is the intended use of this field? If it is to help users find
collections which they may access, then it may be best to be as inclusive as
possible. If it is to aid in the process of selecting collections for other
purposes, perhaps other values would be more useful. It would be nice to
keep the list of values short and easy to understand.

Public (open to the world)
Restricted (restricted by location or affiliation)
Dark (administrative/curatorial access only)
Mixed
Mixed - Mostly Public
Mixed - Mostly Private
Mixed - Mostly Dark

"Mixed" could also be implied. That is, if the value is "Public", it would
mean fully public or mostly public, by definition.

The HathiTrust Rights table includes reasons. In the NDSA context, it may be
that a collection is "dark" but only because resources are not available to
provide public access, but if resources were available, it would be public.
This might be important depending on how the field will be used.

http://www.hathitrust.org/rights_database

In summary, there are many possible variations, but I'm advocating for
keeping it simple.

John

On Fri, Jul 8, 2011 at 4:31 PM, Grotke, Abigail <[log in to unmask]> wrote:

> Re: Collection Availability, I think the original intent (with the NDIIPP
> collections portal) was to have it reflect access restrictions overall.
>
> In the NDIIPP collections display, the meaning of the "Availability"options
> are:
> Online - open and available to anyone via the web
> Onsite - must go onsite to view, but available to anyone
> Research Use - this is mostly the DataPass content...
> Restricted Access - no current access (we didn't want to say completely
> dark, but essentially that's it).
>
> For NSDA purposes some of these may work but there may be other categories
> to consider?
>
> Abbie
>
> -----Original Message-----
> From: The NDSA Content working group list [mailto:
> [log in to unmask]] On Behalf Of Brett Abrams
> Sent: Thursday, July 07, 2011 8:34 AM
> To: [log in to unmask]
> Subject: Re: [NDSA-CONTENT] Please comment or respond by 7/22: Content
> Registry Fields
>
> I think it would be useful to have a separate restrictions field. We might
> also consider a specific ID filed, such as the ID used in the repository
> catalog.
>
> Brett
>
> >>> John L Faundeen <[log in to unmask]> 7/6/2011 2:11 PM >>>
> All,
>
> Regarding the fields, some collections may not have a URL related to them.
> Also, the "Collections Location" field is fine as long as we explain, like
> the parenthesis () do, that this field is not seeking where the collection
> currently is housed which is what the field first implied to me.  Lastly,
> the "Collection Availability" seems to include both how ones gets to the
> collection and if there are any restrictions involved. Those are two,
> potentially different, items.  The field works as long as we understand it
> carries a dual meaning.
>
> John Faundeen, Archivist
> U.S. Geological Survey
> Earth Resources Observation and Science Center 47914-252nd Street Sioux
> Falls, SD 57198 USA
> Tel: 605-594-6092/Fax: [log in to unmask]
>             https://profile.usgs.gov/faundeen ~Records Management - The
> systematic control of records throughout their lifecycle...ARMA.~
>
>
>
> From:
> "Cornwall, Daniel D (EED)" <[log in to unmask]>
> To:
> [log in to unmask]
> Date:
> 07/06/2011 11:53 AM
> Subject:
> [NDSA-CONTENT] Please comment or respond by 7/22: Content Registry Fields
> Sent by:
> The NDSA Content working group list
> <[log in to unmask]>
>
>
>
> Hi All,
>
>
>
> After this morning's meeting I posted a cleaned up version of our
> proposed Recollection fields to
> http://www.loc.gov/extranet/wiki/osi/ndiip/ndsa/index.php?title=Content_
> Registry_Fields.
>
>
>
> Our action team invites your comments either on the wiki, in reply to
> this e-mail or direct comments to [log in to unmask] Bering in
> mind some of us will be extra busy in DC next week, we're taking
> comments through July 22, 2011. Then I'll assemble the feedback into an
> alliance wide survey to be sent out 7/25 or 7/26. I'll be out of the
> office 7/27-8/5. - Daniel
>
>
>
> =======================================
>
> Daniel Cornwall
>
> Head of Technical and Imaging Services
>
> Division of Libraries, Archives and Museums
>
> PO Box 110571
> Juneau, AK 99811-0571
> Phone (907) 465-6332
>
> Fax (907) 465-2665
> E-Mail: [log in to unmask] <mailto:[log in to unmask]>
>
> Web: http://lam.alaska.gov <http://lam.alaska.gov/> .
>
> NOTE: I first check e-mail at 9:30am. If you need to reach me before
> then, please call.
>
>
>
>
>
>
>
>
>
>
>
> ############################
>
> To unsubscribe from the NDSA-CONTENT list:
> write to: mailto:[log in to unmask]
> or click the following link:
>
> http://list.digitalpreservation.gov/SCRIPTS/WA-DIGITAL.EXE?SUBED1=NDSA-CONTENT&A=1
>
> [attachment "image001.gif" deleted by John L Faundeen/GEOG/USGS/DOI]
>
>
> ############################
>
> To unsubscribe from the NDSA-CONTENT list:
> write to: mailto:[log in to unmask]
> or click the following link:
>
> http://list.digitalpreservation.gov/SCRIPTS/WA-DIGITAL.EXE?SUBED1=NDSA-CONTENT&A=1
>
> ############################
>
> To unsubscribe from the NDSA-CONTENT list:
> write to: mailto:[log in to unmask]
> or click the following link:
>
> http://list.digitalpreservation.gov/SCRIPTS/WA-DIGITAL.EXE?SUBED1=NDSA-CONTENT&A=1
>
> ############################
>
> To unsubscribe from the NDSA-CONTENT list:
> write to: mailto:[log in to unmask]
> or click the following link:
>
> http://list.digitalpreservation.gov/SCRIPTS/WA-DIGITAL.EXE?SUBED1=NDSA-CONTENT&A=1
>

############################

To unsubscribe from the NDSA-CONTENT list:
write to: mailto:[log in to unmask]
or click the following link:
http://list.digitalpreservation.gov/SCRIPTS/WA-DIGITAL.EXE?SUBED1=NDSA-CONTENT&A=1

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

April 2021
March 2021
February 2021
January 2021
September 2020
June 2020
February 2019
May 2018
March 2018
February 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
July 2015
June 2015
May 2015
March 2015
February 2015
January 2015
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014, Week 2
March 2014, Week 1
March 2014
February 2014, Week 4
February 2014, Week 2
February 2014, Week 1
January 2014, Week 4
January 2014, Week 3
January 2014, Week 2
January 2014, Week 1
December 2013, Week 1
November 2013, Week 2
November 2013, Week 1
October 2013, Week 5
October 2013, Week 3
October 2013, Week 2
September 2013, Week 5
September 2013, Week 4
September 2013, Week 3
August 2013, Week 5
August 2013, Week 4
August 2013, Week 3
August 2013, Week 2
August 2013, Week 1
July 2013, Week 5
July 2013, Week 4
July 2013, Week 3
July 2013, Week 2
July 2013, Week 1
June 2013, Week 3
June 2013, Week 2
June 2013, Week 1
May 2013, Week 4
May 2013, Week 3
May 2013, Week 2
May 2013, Week 1
April 2013, Week 5
April 2013, Week 4
April 2013, Week 3
April 2013, Week 2
April 2013, Week 1
March 2013, Week 5
March 2013, Week 2
March 2013, Week 1
February 2013, Week 3
February 2013, Week 2
January 2013, Week 5
January 2013, Week 4
January 2013, Week 3
January 2013, Week 2
December 2012, Week 1
November 2012, Week 5
November 2012, Week 3
November 2012, Week 2
November 2012, Week 1
October 2012, Week 5
October 2012, Week 4
October 2012, Week 1
September 2012, Week 3
September 2012, Week 2
September 2012, Week 1
August 2012, Week 5
August 2012, Week 4
August 2012, Week 2
August 2012, Week 1
July 2012, Week 5
July 2012, Week 3
July 2012, Week 1
June 2012, Week 3
June 2012, Week 2
June 2012, Week 1
May 2012, Week 2
May 2012, Week 1
April 2012, Week 4
April 2012, Week 3
April 2012, Week 2
April 2012, Week 1
March 2012, Week 4
March 2012, Week 3
March 2012, Week 2
March 2012, Week 1
February 2012, Week 2
February 2012, Week 1
January 2012, Week 5
January 2012, Week 4
January 2012, Week 3
January 2012, Week 2
January 2012, Week 1
December 2011, Week 5
December 2011, Week 3
December 2011, Week 2
December 2011, Week 1
November 2011, Week 3
November 2011, Week 1
October 2011, Week 5
October 2011, Week 3
October 2011, Week 2
October 2011, Week 1
September 2011, Week 5
September 2011, Week 4
September 2011, Week 3
September 2011, Week 2
September 2011, Week 1
August 2011, Week 4
August 2011, Week 3
August 2011, Week 1
July 2011, Week 4
July 2011, Week 3
July 2011, Week 2
July 2011, Week 1
June 2011, Week 4
June 2011, Week 2
June 2011, Week 1
May 2011, Week 5
May 2011, Week 1
April 2011, Week 4
April 2011, Week 3
April 2011, Week 2
April 2011, Week 1
March 2011, Week 5
March 2011, Week 1
February 2011, Week 2
February 2011, Week 1
January 2011, Week 3
January 2011, Week 2
January 2011, Week 1
December 2010, Week 3
December 2010, Week 2
December 2010, Week 1
November 2010, Week 3
November 2010, Week 2
November 2010, Week 1
October 2010, Week 5
October 2010, Week 4
October 2010, Week 2
September 2010, Week 4
September 2010, Week 3
September 2010, Week 2
September 2010, Week 1
August 2010, Week 5

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager