Comments on: Introducing Omeka http://www.dancohen.org/2008/02/20/introducing-omeka/ Covering the intersection of digital technology and research, teaching, and learning in the humanities, including search, data mining, website development and design, and programming. Fri, 04 Jul 2008 15:16:22 +0000 http://wordpress.org/?v=2.5.1 By: 益学会 > OLDaily 中文版 » Blog Archive http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1833 益学会 > OLDaily 中文版 » Blog Archive Tue, 11 Mar 2008 14:05:27 +0000 http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1833 [...] Dan Cohen, Weblog March 5, 2008 [原文链接] [...] [...] Dan Cohen, Weblog March 5, 2008 [原文链接] [...]

]]> By: Social Software in Libraries » links for 2008-02-24 http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1758 Social Software in Libraries » links for 2008-02-24 Mon, 03 Mar 2008 21:22:39 +0000 http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1758 [...] Dan Cohen’s Digital Humanities Blog » Blog Archive » Introducing Omeka (tags: chapter2) [...] [...] Dan Cohen’s Digital Humanities Blog » Blog Archive » Introducing Omeka (tags: chapter2) [...]

]]> By: Dan Cohen’s Digital Humanities Blog » Blog Archive » Video Intro to Omeka http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1721 Dan Cohen’s Digital Humanities Blog » Blog Archive » Video Intro to Omeka Tue, 26 Feb 2008 23:27:55 +0000 http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1721 [...] through the installation and customization of Omeka, which Jeremy and Dave work on, and which just launched recently. (And it’s off to a fantastic start, with active forums and nearly 300 downloads in under a [...] [...] through the installation and customization of Omeka, which Jeremy and Dave work on, and which just launched recently. (And it’s off to a fantastic start, with active forums and nearly 300 downloads in under a [...]

]]> By: Metadata Nuggets » Blog Archive » Omeka http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1715 Metadata Nuggets » Blog Archive » Omeka Mon, 25 Feb 2008 17:00:52 +0000 http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1715 [...] specialists in mind, allowing users to focus on content rather than programming. Dan Cohen has a nice blog post with visuals about Omeka. Omeka comes loaded with the following [...] [...] specialists in mind, allowing users to focus on content rather than programming. Dan Cohen has a nice blog post with visuals about Omeka. Omeka comes loaded with the following [...]

]]> By: Relaxing on the Trail » Omeka is Public http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1709 Relaxing on the Trail » Omeka is Public Fri, 22 Feb 2008 19:03:16 +0000 http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1709 [...] Dan Cohen did such a great job introducing his readers to Omeka, I will send you to his Feb 20 post to read more. When you’re finished, head over to the [...] [...] Dan Cohen did such a great job introducing his readers to Omeka, I will send you to his Feb 20 post to read more. When you’re finished, head over to the [...]

]]> By: Jim Safley http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1705 Jim Safley Thu, 21 Feb 2008 21:23:26 +0000 http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1705 @Bruce: Thanks so much for the comments and points. The Omeka team has been discussing these very things, and we appreciate your input. Let me respond to your points: 1) Experience tells us that individuals and small cultural institutions shy away from collection systems that emphasize esoteric schema. To balance their needs with the needs of advanced users, Omeka offers a generalized, easy-to-use schema that includes a permanent Dublin Core element set (the "flat fields") that are common to all items, as well as customized item types to which users may assign customized metadata element sets (the "relational" metadata). This way, we feel, the average user will not be overwhelmed by strict metadata standards, while the more advanced users may customize their item types to whatever standards they wish. 2) We agree with you that this is a weakness, and we will be focusing more on localization in the future. 3) We have a ticket on Trac to add an Atom feed. And there is a RDF Dublin Core output that you may not be aware of (using ?output=dc). We intend to add more outputs as time allows. We welcome any further comments or ideas. Please feel free to post on our forums: http://omeka.org/forums/ Best, Jim Safley Omeka Developer Center for History and New Media @Bruce:

Thanks so much for the comments and points. The Omeka team has been discussing these very things, and we appreciate your input. Let me respond to your points:

1) Experience tells us that individuals and small cultural institutions shy away from collection systems that emphasize esoteric schema. To balance their needs with the needs of advanced users, Omeka offers a generalized, easy-to-use schema that includes a permanent Dublin Core element set (the “flat fields”) that are common to all items, as well as customized item types to which users may assign customized metadata element sets (the “relational” metadata). This way, we feel, the average user will not be overwhelmed by strict metadata standards, while the more advanced users may customize their item types to whatever standards they wish.

2) We agree with you that this is a weakness, and we will be focusing more on localization in the future.

3) We have a ticket on Trac to add an Atom feed. And there is a RDF Dublin Core output that you may not be aware of (using ?output=dc). We intend to add more outputs as time allows.

We welcome any further comments or ideas. Please feel free to post on our forums:
http://omeka.org/forums/

Best,
Jim Safley
Omeka Developer
Center for History and New Media

]]> By: Dan Cohen http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1704 Dan Cohen Thu, 21 Feb 2008 15:57:46 +0000 http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1704 @Wally: Oops. Thanks for the correction. I think I meant to write Cultural & Heritage Museums of South Carolina. That's a great idea about using Omeka as an exhibit front end for DSpace. Let the Omeka team know if you need any help. @Bruce: You should raise these issues on the Omeka forums (though I'll of course forward them to the Omeka team). The Zotero and Omeka teams are completely distinct, and so there perhaps has not been enough cross-pollination. But these seem like things the Omeka team can address quickly. @Wally: Oops. Thanks for the correction. I think I meant to write Cultural & Heritage Museums of South Carolina. That’s a great idea about using Omeka as an exhibit front end for DSpace. Let the Omeka team know if you need any help.

@Bruce: You should raise these issues on the Omeka forums (though I’ll of course forward them to the Omeka team). The Zotero and Omeka teams are completely distinct, and so there perhaps has not been enough cross-pollination. But these seem like things the Omeka team can address quickly.

]]> By: Jerry Yarnetsky http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1703 Jerry Yarnetsky Thu, 21 Feb 2008 15:31:26 +0000 http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1703 Good timing! We're looking to get away from ContentDM this year as we can no longer afford the licensing fees. This looks great! Good timing! We’re looking to get away from ContentDM this year as we can no longer afford the licensing fees. This looks great!

]]> By: Bruce D'Arcus http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1702 Bruce D'Arcus Thu, 21 Feb 2008 11:57:51 +0000 http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1702 Really nice Dan! A few random gripes, though, looking through the SQL schema: First, the metadata support is just a series of flat fields. In a relational database? I would have thought the Zotero experience would have shown the practical limitations of this sort of modeling? Second, this is a familiar issue of mine, but I noticed first/middle/last name columns in one of the tables. I know this is common in (particularly) U.S. based web design, but it's not very international-friendly. Third: RSS2? I would have thought a new tool like this would have logically supported Atom as default (and perhaps the RDF RSS flavor). Really nice Dan!

A few random gripes, though, looking through the SQL schema:

First, the metadata support is just a series of flat fields. In a relational database? I would have thought the Zotero experience would have shown the practical limitations of this sort of modeling?

Second, this is a familiar issue of mine, but I noticed first/middle/last name columns in one of the tables. I know this is common in (particularly) U.S. based web design, but it’s not very international-friendly.

Third: RSS2? I would have thought a new tool like this would have logically supported Atom as default (and perhaps the RDF RSS flavor).

]]> By: Finding America » Blog Archive » Omeka Goes Public with release 0.9.0 http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1701 Finding America » Blog Archive » Omeka Goes Public with release 0.9.0 Thu, 21 Feb 2008 05:29:30 +0000 http://www.dancohen.org/2008/02/20/introducing-omeka/#comment-1701 [...] places, including the Official Omeka Blog, Inside Higher Ed, Found History, Steve Lawson, and Dan Cohen’s blog. Tom gives a great overview of the project, and how it fits into our former director Roy [...] [...] places, including the Official Omeka Blog, Inside Higher Ed, Found History, Steve Lawson, and Dan Cohen’s blog. Tom gives a great overview of the project, and how it fits into our former director Roy [...]

]]>