<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Book Antiqua";
panose-1:2 4 6 2 5 3 5 3 3 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p.BlockQuote, li.BlockQuote, div.BlockQuote
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
punctuation-wrap:simple;
text-autospace:none;
font-size:12.0pt;
font-family:"Book Antiqua";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Hi, Sue, <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I checked the page out that you gave me. .
. . </span></font><font size=2 color=navy face=Wingdings><span
style='font-size:10.0pt;font-family:Wingdings;color:navy'>J</span></font><font
size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Yesterday, we had a discussion about
creating materials for Communities to use . . . and, I’m not sure this is
it, at least, not as a final output. I think that if it has an export function,
that it could be really useful for the middle-level data collection that would
then be used to create the Community materials. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>My first observation of the site was that
it looked very much like the search and retrieval system our library uses here
at NMSU. These systems are an outgrowth of the Retrieve/Browse paradigm of
early computer systems when there really was a space/functionality constraint.
(My first invoice/cash application had 32K of computer memory. That’s
1/100<sup>th</sup> of what I have today on this laptop; which I don’t have
to share). <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>First, I searched for one of my favorite
polysemic words, “object”, and didn’t find anything.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Then, I read that the words were about the
Southwest, so I searched for “cactus”. “Cactus” showed
up at the top of the retrieved list which then went on to show such things as
California Redwoods. Every once in a very great while I find this kind of option
useful, but usually only to confirm the bad news, that what I was looking for
isn’t there. I thought perhaps the alphabetic listing might be useful for
helping people correct spelling errors, so I went back and looked for “cactus”.
I didn’t find anything, which surprised me. This means that the
application is using a database that supports browse after keyed access. IBM’s
DB2 used to have that facility. . . . Most non-commercial applications aren’t
coded this way; this kind of functionality is useful when you have multiple items
coded under an identifying key, as for example Customer #/Invoice 1, Customer #/Invoice
2, and so on. It might also be useful for Cactus:Cholla, Cactus:Sequaro,
Cactus:Rainbow. But it doesn’t appear to be working that way . . . . back
soon . . . I put in “cactus” again and selected the “Each
term followed by its relationships” radio button. Again, I got the
StartKey:Browse List configuration. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Interestingly enough, you can input “c”
and get a list of items beginning with that letter. You can input “ce”
and get the list commencing with “ce”. . . but if you input “cectus”,
you get item not found. . . . I wondered if the function was perhaps dependent
on input string length. I input “cec” and again got a Not Found. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I have some issues with the list of
metadata types. These are all highly abstracted, culturally embedded terms. I’ll
bet there is only one entry for “preferred term”. . . Having spent
several to many years in an institution that is famous for its critical
pedagogy, I have to has, Preferred By WHOM? It also is limited in that to make
the categories work for different disciplines, you have to identify each one of
them as a language. Lastly, I tracked through these categories long enough to
realize that the relationships form a Network. Both the search keys and the outputs
are all terms. I did find a place where there was a description. I found it
kind of frustrating because I felt like I was “always on the road”
never “at the <st1:place w:st="on">Inn</st1:place>”. In other
words, I was always searching, always searching, and because the responses were
so broad, and crossed so many categories, I never felt like I was done. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'> PT – Preferred Term<br>
SY – Synonym<br>
BT – Broader Term<br>
NT – Narrower Term<br>
FR – Functionally Related<br>
CR – Conceptually Related<br>
TR – Temporally Related<br>
PS – Physically/Spatially Related<font
color=navy><span style='color:navy'><o:p></o:p></span></font></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>You mentioned that this was pretty easy to
use. . . there is a kind of Rule of Interaction in Computer Science that says
that the easier something is to assemble on the front end, the less sophisticated
the functionality will be on the back end. I was a bit worried that there
was a Search Everywhere option, that allowed you to go to Google. IMHO, this is
an hypertext application without the graphics and sophisticated search engine
tools. It probably doesn’t even allow you to embed special fonts for languages
that require characters other than those supported even by Unicode. (like
Athapascan languages). Given the sophistication of today’s technologies, I
don’t think users will want this for anything more than the mid-level
interface tool . . . <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>A final, final note: This is very Modern
(one view, one meaning) as opposed to PostModern (many voices) and
PostStructuralist (lots of pieces, diachronic component). <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>It seems you might like a Wiki better. . .
it gives you places for people to participate. The people I have worked with
always seem to think there is only one word for something in their language,
and one way to say that word. The battles that ensue around this idea tend to
halt revitalization rather than facilitate it. . . Oh: SWT doesn’t seem
to have a place for sound. . . . no pictures? All Text? <o:p></o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> <st1:PersonName
w:st="on">Indigenous Languages and Technology</st1:PersonName>
[mailto:ILAT@LISTSERV.ARIZONA.EDU] <b><span style='font-weight:bold'>On Behalf
Of </span></b>Susan Penfield<br>
<b><span style='font-weight:bold'>Sent:</span></b> Sunday, February 26, 2006
8:29 AM<br>
<b><span style='font-weight:bold'>To:</span></b> ILAT@LISTSERV.ARIZONA.EDU<br>
<b><span style='font-weight:bold'>Subject:</span></b> [ILAT] Software</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Hi,<br>
Yesterday I mentioned that I have been looking at a new software which might be
usable <br>
for creating thematic dictionaries (a very user-friendly option) . I would like
some others to take a look<br>
to see what they think of it . Check out <a href="http://www.swt.arizona.edu">www.swt.arizona.edu</a>.
<br>
Best,<br>
Susan<br clear=all>
<br>
-- <br>
Susan D. Penfield, Ph.D.<br>
<br>
Department of English<br>
Affiliate faculty: Department of Linguistics <br>
and the Second Language Acquisition and Teaching Program <br>
American Indian Language Development Institute<br>
Phone for messages: (520) 621-1836 <o:p></o:p></span></font></p>
</div>
</body>
</html>