<?xml version="1.0" encoding="utf-8" standalone="no"?>
<!DOCTYPE document PUBLIC "-//CNX//DTD CNXML 0.5//EN" "http://cnx.rice.edu/technology/cnxml/schema/dtd/0.5/cnxml_plain.dtd">
<document xmlns="http://cnx.rice.edu/cnxml" xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" id="new">
  <name>Collection description</name>
  <metadata>
  <md:version>1.2</md:version>
  <md:created>2006/05/21 00:43:20 GMT-5</md:created>
  <md:revised>2006/05/23 01:52:17.971 GMT-5</md:revised>
  <md:authorlist>
      <md:author id="jgrimes">
      <md:firstname>Joseph</md:firstname>
      <md:othername>E.</md:othername>
      <md:surname>Grimes</md:surname>
      <md:email>joe_grimes@sil.org</md:email>
    </md:author>
  </md:authorlist>

  <md:maintainerlist>
    <md:maintainer id="jgrimes">
      <md:firstname>Joseph</md:firstname>
      <md:othername>E.</md:othername>
      <md:surname>Grimes</md:surname>
      <md:email>joe_grimes@sil.org</md:email>
    </md:maintainer>
  </md:maintainerlist>
  
  <md:keywordlist>
    <md:keyword>description</md:keyword>
    <md:keyword>key words</md:keyword>
    <md:keyword>keywords</md:keyword>
    <md:keyword>remarks</md:keyword>
  </md:keywordlist>

  <md:abstract>Titles are not informative enough for the Wordcorr community. Each collection needs a concise description, key words by which it can be located, and remarks on anything else that might be helpful.</md:abstract>
</metadata>
  <content>
    <figure id="element-732"><media type="image" src="Coll-Descr.jpg"/>
<caption>Key words, description, and remarks from the Collection page of JG-SulSel12.</caption></figure><para id="delete_me">Names and titles are often not informative enough that a person who might profit from the contents of a collection can get a clear idea what is (and is not) in it. So Wordcorr requires a paragraph or more to <term>describe</term> the contents. It doesn’t have to be long, just long enough to be useful.</para><para id="element-111">If you were doing a Google search for your collection, using just a regular Web browser like Firefox and not a special search engine developed for linguistics, what words would you use in the search? Put those in the Keywords field. Think about what other <term>key word</term>s might lead people to your collection too. Separate the key words (or phrases) with comma space.</para><para id="element-223">There is also an optional <term>Remarks</term> field for essential information that doesn’t fit standard library categories. For example, early versions of WordSurv, and many collections imported from spreadsheets, were made at a time when linguists had no access to character sets for the International Phonetic Alphabet (<term>IPA</term>) in Unicode. So linguists each made up their own private conventions, things like capital “N” for angma, capital “E” for epsilon, “q” or “7” for glottal stop. There was no way they could standardize among themselves. So any collection with that kind of history needs an explanation of the original symbols in its Remarks field. From experience, we recommend that you put it in even if you think you’ve gone through and converted everything to IPA – it’s not impossible that you might have missed a few.</para><para id="element-728">Anything else that linguists who use your data fifty years from now should know about your collection also goes into Remarks.</para>   
  </content>
  
</document>
