Hi everyone,

All the ideas in this thread sound great. I'm wondering if two very informal gatherings in Minneapolis might be useful for two nested groups of us--something like:

- one in which we could share ideas about conceptual aspects of home-built museum data management tools, as a broadly scoped conversation about whatever open-source software or shrink-wrapped development environments we're using, and especially about how standards figure concretely in what we're doing (or might do) with them; and

- one in which (following Ann's initial idea) folks who are using FileMaker could share knowledge and ask each other questions about using it to serve museum needs, since many real nuts-and-bolts aspects of doing so are wholly specific to that software.

The key issue of standards bears strongly on both topics, but we could steer them towards the first gathering (that way everyone interested could take part in that discussion, but people who don't use FileMaker wouldn't be subjected to tales of FileMaker-specific techniques--and those do use it would have more time to talk about such things).

If this makes sense, are there volunteers to serve as point people by collecting initial ideas for discussion (and checking with the conference planners to see about scheduling windows when we could plan to gather informally without crashing into other things)?

just thinking out loud,
Rob

At 21:33 -0700 4/7/04, Mary Elings wrote:

As co-chair of the Stds&Controlled Vocabulary SIG, I think a get together
at MCN would be great....

--
_________________________________________________________________
Rob Lancefield     [email protected]   Wesleyan University
Registrar of Collections / Manager of Museum Information Services
Davison Art Center                           www.wesleyan.edu/dac
301 High Street, Middletown CT 06459 USA        tel. 860.685.2965
Board of Directors, Museum Computer Network           www.mcn.edu


---
You are currently subscribed to mcn_mcn-l as: [email protected]
To unsubscribe send a blank email to 
[email protected]

Reply via email to