RECMGMT-L Archives

Records Management

RECMGMT-L@LISTSERV.IGGURU.US

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Grevin, Fred" <[log in to unmask]>
Reply To:
Records Management Program <[log in to unmask]>
Date:
Mon, 16 Mar 2009 09:11:42 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (92 lines)
Jesse, I tried to locate the NISO publication you cite, but it's not
available (I tried both your URL and running a search for the title).

Did you perhaps intend to cite NISO RP-2005-02 "Search and Retrieval
Results Set Metadata", which the NISO abstract describes as "Defines a
core set of metadata elements that provide information about a result
set at both the aggregate level and the individual record to provide
better quality of information returned and ensure more standardized
presentation of results to the end user. These data elements are
intended to be used by content providers to provide better quality of
information returned through a variety of methods. They may also used to
ensure that the needs of metasearch products are met by a given
protocol." ?

Best regards.

Fred
===================================================================
Frederic J. Grevin
Deputy Commissioner and Chief Information Officer
The City of New York,
Department of Records
Email: [log in to unmask]
Land phone: 212.788.8615
Cell phone: 347.436.5360
Fax:  212.788.8614
www.nyc.gov/records
31 Chambers Street
New York, NY 10007
USA
-----Original Message-----
From: Records Management Program [mailto:[log in to unmask]] On
Behalf Of Jesse Wilkins
Sent: Friday, March 13, 2009 18:28
To: [log in to unmask]
Subject: Re: [RM] Metadata for Records Management

Hi Pat,
I own both of them and they are more of a framework for determining
metadata, with representative but not dispositive values. From ISO
23081-2:
"While this Technical Specification contains a simple set of descriptive
metadata elements, specific application domains need to define their
own descriptive metadata elements."

You might look at the NISO "Guidelines for Understanding Metadata" at
http://www.niso.org/publications/press/UnderstandingMetadata.pdf;<http:/
/www.niso.org/publications/press/UnderstandingMetadata.pdf>
while
not providing a definitive list either, it does introduce a number of
other
guidelines and shows examples from them.

Couple more points to consider:
1. They are copyrighted and not available for casual redistribution;
then
again, they might be a valuable acquisition for your library and they
are
not egregiously expensive.

2. You don't mention what the usage is, but if it is to define metadata
fields for an application, I think it's always worthwhile to mention
that
the more fields are provided, the more users will resist filling them
all
in. Automation is definitely advised wherever possible.

And one last troll-point: AIIM offers modules on metadata as part of
several
of its courses, notably the ERM, ECM, and IOA courses. The modules are
also
available as individual courses for a substantially lower fee. Anyone
who
wants more information on those please feel free to contact me directly.

Cheers,

Jesse Wilkins
[log in to unmask]

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
To unsubscribe from this list, click the below link. If not already
present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of
the message.
mailto:[log in to unmask]

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
To unsubscribe from this list, click the below link. If not already present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the message.
mailto:[log in to unmask]

ATOM RSS1 RSS2