summary pages

[Steven Bird]

Its nice to see some activity on this mailing list!

A page of ISO-639-3 codes for which no information is available would
be empty, thanks to the Ethnologue.

We could speculate about frequency-sorted lists, but any
implementation would run into problems for languages where IMDI is
providing metadata for individual sessions, contravening OLAC's
granularity requirement "A metadata repository should treat resources
with a single provenance as constituting a single unit with respect to
OLAC metadata and should, therefore, describe them within a single
record. " (http://www.language-archives.org/OLAC/repositories.html#Guidelines%20concerning%20relevance%20and%20granularity).
 For example:

http://www.language-archives.org/language/bea

I propose that you describe a few such reports in more detail as a
feature request in the OLAC Issue Tracker at:
http://code.google.com/p/olac/issues/entry?template=Feature%20Request

Thanks,
-Steven Bird

On 4 November 2010 09:53, Nick Thieberger <thien at unimelb.edu.au> wrote:
> I really like using the OLAC pages which summarise information
> available for any language based on the aggregated metadata
> (http://www.language-archives.org/language/[XXX]). This in itself is a
> powerful argument for using OLAC standards (as I will be arguing next
> week at the CTLDC meeting in Tokyo).
>
> I am wondering if there is also a way of generating pages based on the
> amount of information available, so that it would be possible to see a
> page of ISO-639-3 codes for which there was no information available?
> Or a list of all languages for which only descriptions occur but not
> other material?
>
> Thanks,
>
> Nick
>