Looking for web-hosting

s.t. bischoff bischoff.st at GMAIL.COM
Mon Apr 25 14:22:28 UTC 2011


I should clarify as I didn't mean to imply that there were "sides" to be
taken. I agree absolutely with Claire's (and Aidan's) comments that the two
are different, and meant to only add that it might be helpful to consider
where similarities occur for purpose of planning for long term resource
maintenance and storage.  Perhaps the misunderstanding comes from the
following  comment:

"The ideal situation would be some combination of both perhaps:  archiving
and community web publication that maintains each directory in terms of best
practices with a commitment to permanence."

To be a bit more clear, what I meant to convey was that if *websites* where
created with best practices in mind it might facilitate a move to archiving
(in various formats). The ideal situation would be some sort of well planned
archiving *and*  creation of websites/online language resources in terms of
agreed upon best practices.

Academic linguists (and others) seem to have a hyper awareness of these
issues (e.g. best practices, archiving vs. website building). I would be
curious to hear how different community members construe these issues or
more generally issues regarding online language resources.

cheers,
Shannon


On Mon, Apr 25, 2011 at 9:27 AM, Aidan Wilson <aidan at usyd.edu.au> wrote:

> I'm tempted to say that no such archive exists that has the level of web
> presence and access to data that you're after, and no web hosting service in
> the world is going to be able to guarantee perpetual hosting of your data,
> and likely not other aspects of an archive either.
>
> So I would side with Claire, and suggest looking into each one
> independently, opting for the best of each, rather than trying to find a
> solution that's 'good enough' and does both.
>
> Web hosting doesn't have quite the same restrictions on data as archiving,
> so satisfying an archive's requirements first is probably a good move, and
> then looking into how you can copy that data to a web hosting service
> (likely down-sampling the files to mp3, etc.) will be relatively easy.
>
> Start by looking for an archive at http://www.language-archives.org/
>
> -Aidan Wilson
>
>
>
>
> On Mon, 25 Apr 2011, s.t. bischoff wrote:
>
>  Good points Claire. It would seem if the directory that allows for a web
>> interface where maintained in the "spirit" of an archive (e.g. following
>> some form of community derived best practices with a commitment to
>> permanence) then web publication could have the permanence that archiving
>> strives for. Such an approach would be an alternative (or perhaps first
>> step
>> to archiving) for communities not ready, willing, or able to place their
>> language resources in the hands of third parties, yet wanting to ensure
>> some
>> sort of permanence for the resources. The ideal situation would be some
>> combination of both perhaps:  archiving and community web publication that
>> maintains each directory in terms of best practices with a commitment to
>> permanence. It seems that even though the two are different in some
>> regards--there is a good deal of overlap in terms of production,
>> maintenance, and use.
>>
>> cheers,
>> Shannon
>>
>> On Sun, Apr 24, 2011 at 8:45 PM, Claire Bowern <clairebowern at gmail.com>
>> wrote:
>>      Just a quick note that we seem to be talking about both
>>      archiving and publication here, and perhaps we should be
>>      thinking about them as two different things. They have different
>>      requirements. For example, with sound files, we would want to
>>      archive the highest quality files possible. But for web
>>      streaming, that's not what we want. It makes it harder
>>      to disperse materials to communities, but web publication
>>      doesn't have he permanence that archiving should do. This would
>>      be a good argument not to look for a single solution, but to
>>      investigate digital archives *and* web dissemination. Claire
>>
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserv.linguistlist.org/pipermail/ilat/attachments/20110425/e40a71a5/attachment.htm>


More information about the Ilat mailing list