<?xml version="1.0"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>Forums Tag: metadata</title>
<link>http://omeka.org/forums/</link>
<description>Forums Tag: metadata</description>
<language>en</language>
<pubDate>Sun, 12 Oct 2008 05:12:45 +0000</pubDate>

<item>
<title>DaveLester on "Metadata extension"</title>
<link>http://omeka.org/forums/topic/metadata-extension#post-641</link>
<pubDate>Sat, 20 Sep 2008 14:24:26 +0000</pubDate>
<dc:creator>DaveLester</dc:creator>
<guid isPermaLink="false">641@http://omeka.org/forums/</guid>
<description>&#60;p&#62;The next release of Omeka will offer greater flexibility in supporting additional metadata schemas in the form of element-sets.  By default, Omeka uses Dubling Core for metadata, and element-sets can be pre-defined schemas used to extend your DC item metadata.  They're added via a plugin, and sound like a good option for your project.&#60;/p&#62;
&#60;p&#62;I'll be in touch with you shortly.&#60;/p&#62;
&#60;p&#62;Best,&#60;br /&#62;
Dave Lester
&#60;/p&#62;</description>
</item>
<item>
<title>glopacadmin on "Metadata extension"</title>
<link>http://omeka.org/forums/topic/metadata-extension#post-635</link>
<pubDate>Wed, 17 Sep 2008 19:55:11 +0000</pubDate>
<dc:creator>glopacadmin</dc:creator>
<guid isPermaLink="false">635@http://omeka.org/forums/</guid>
<description>&#60;p&#62;Hi.&#60;br /&#62;
We are in the process of developing a metadata schema for multilingual performing arts subject matter and think that Omeka would make a good use target for this. The objective would be to allow the use of this metadata schema for individual collections to import and extend their performing arts metadata, and then to be able to expose the generated metadata to Web services or other sharing mechanisms. &#60;/p&#62;
&#60;p&#62;Would the Omeka team be interested in joining some discussions about implementation and use? We can be contacted at my username at cornell dot edu or at glopac at cornell dot edu.
&#60;/p&#62;</description>
</item>
<item>
<title>TomScheinfeldt on "Associating Metadata With Batch Uploaded Files"</title>
<link>http://omeka.org/forums/topic/associating-metadata-with-batch-uploaded-files#post-626</link>
<pubDate>Mon, 15 Sep 2008 11:26:18 +0000</pubDate>
<dc:creator>TomScheinfeldt</dc:creator>
<guid isPermaLink="false">626@http://omeka.org/forums/</guid>
<description>&#60;p&#62;Lyn--&#60;/p&#62;
&#60;p&#62;It is underway. In the next few days we will be releasing version 0.10.0 alpha to the dev list for developer community testing and refinement. This new version of Omeka includes a completely new metadata architecture, prerequisite to CONTENTdm interoperability. (Don't worry, version 0.10.0 comes with a set of migration tools for current users of version 0.9.x.) When version 0.10.0 is released as a public beta later in the fall, it will also include the CONTENTdm migration tools.&#60;/p&#62;
&#60;p&#62;Watch this space.&#60;/p&#62;
&#60;p&#62;Take care,&#60;br /&#62;
Tom Scheinfeldt
&#60;/p&#62;</description>
</item>
<item>
<title>Lmaccorkle on "Associating Metadata With Batch Uploaded Files"</title>
<link>http://omeka.org/forums/topic/associating-metadata-with-batch-uploaded-files#post-625</link>
<pubDate>Sun, 14 Sep 2008 18:25:57 +0000</pubDate>
<dc:creator>Lmaccorkle</dc:creator>
<guid isPermaLink="false">625@http://omeka.org/forums/</guid>
<description>&#60;p&#62;What happened to the CONTENTdm migration tools project?  I want to use it  for the first time to enhance a special collection where the metadata and images are stored in CONTENTdm.&#60;/p&#62;
&#60;p&#62;Thanks, Lyn
&#60;/p&#62;</description>
</item>
<item>
<title>jpeg2000 on "Associating Metadata With Batch Uploaded Files"</title>
<link>http://omeka.org/forums/topic/associating-metadata-with-batch-uploaded-files#post-603</link>
<pubDate>Wed, 20 Aug 2008 12:53:02 +0000</pubDate>
<dc:creator>jpeg2000</dc:creator>
<guid isPermaLink="false">603@http://omeka.org/forums/</guid>
<description>&#60;p&#62;Thanks, Tom! That sounds pretty great. I'll keep an eye out for it, and look forward to giving those migration tools a spin. &#60;/p&#62;
&#60;p&#62;jason (jpeg2000)&#60;br /&#62;
jkucsma_at_metro.org
&#60;/p&#62;</description>
</item>
<item>
<title>JeremyBoggs on "Definition List tags vs. H2 tags"</title>
<link>http://omeka.org/forums/topic/definition-list-tags-vs-h2-tags#post-602</link>
<pubDate>Tue, 19 Aug 2008 17:07:12 +0000</pubDate>
<dc:creator>JeremyBoggs</dc:creator>
<guid isPermaLink="false">602@http://omeka.org/forums/</guid>
<description>&#60;p&#62;Hi myotus,&#60;/p&#62;
&#60;p&#62;While I think using a definition list is OK in this instance, I'm not sure that it would really be &#34;cleaner.&#34; I personally am reluctant to use definition lists except for 1) acutally definiting terms, or 2) marking up dialogue or conversation. This follows the &#60;a href=&#34;http://www.w3.org/TR/REC-html40/struct/lists.html#h-10.3&#34;&#62;W3C's recommentation&#60;/a&#62;. Regardless, you could mark up the items/show page with definition lists and style accordingly, and it would work fine.
&#60;/p&#62;</description>
</item>
<item>
<title>TomScheinfeldt on "Associating Metadata With Batch Uploaded Files"</title>
<link>http://omeka.org/forums/topic/associating-metadata-with-batch-uploaded-files#post-587</link>
<pubDate>Tue, 12 Aug 2008 23:12:04 +0000</pubDate>
<dc:creator>TomScheinfeldt</dc:creator>
<guid isPermaLink="false">587@http://omeka.org/forums/</guid>
<description>&#60;p&#62;jpeg2000--&#60;/p&#62;
&#60;p&#62;We're working very hard towards the 0.10.0 release which will feature a new data architecture more amenable to CONTENTdm import and export.  Once that's finished sometime early in the new semester, our first priority will be a suite of CONTENTdm migration tools.  I can't give a precise date, but sometime before Thanksgiving would be a safe bet.&#60;/p&#62;
&#60;p&#62;Take care,&#60;br /&#62;
Tom
&#60;/p&#62;</description>
</item>
<item>
<title>jpeg2000 on "Associating Metadata With Batch Uploaded Files"</title>
<link>http://omeka.org/forums/topic/associating-metadata-with-batch-uploaded-files#post-585</link>
<pubDate>Tue, 12 Aug 2008 15:08:55 +0000</pubDate>
<dc:creator>jpeg2000</dc:creator>
<guid isPermaLink="false">585@http://omeka.org/forums/</guid>
<description>&#60;p&#62;I read Tom's post here, and I'm wondering what sort of movement there has been on the CONTENTdm migration tool. I have several CDM collections that I would like to keep in their legacy system while allowing users to access the collections via Omeka.
&#60;/p&#62;</description>
</item>
<item>
<title>myotus on "Definition List tags vs. H2 tags"</title>
<link>http://omeka.org/forums/topic/definition-list-tags-vs-h2-tags#post-570</link>
<pubDate>Tue, 05 Aug 2008 19:18:12 +0000</pubDate>
<dc:creator>myotus</dc:creator>
<guid isPermaLink="false">570@http://omeka.org/forums/</guid>
<description>&#60;p&#62;I was wondering.... As I am working with Omeka and styling it, it seems to me that the metadata would be cleaner and better structured wtih Definition List tags rather than h2 tags both from styling and accessibility standpoints.&#60;/p&#62;
&#60;p&#62;&#38;lt;b&#38;gt;H2 Heading tag:&#38;lt;/b&#38;gt;&#60;br /&#62;
&#60;pre&#62;&#60;code&#62;&#38;lt;div id=&#38;quot;publisher&#38;quot; class=&#38;quot;field&#38;quot;&#38;gt;
&#38;lt;h2&#38;gt;Publisher&#38;lt;/h2&#38;gt;
&#38;lt;div class=&#38;quot;field-value&#38;quot;&#38;gt;&#38;lt;p&#38;gt;Minnesota Historical Society&#38;lt;/p&#38;gt;&#38;lt;/div&#38;gt;
&#38;lt;/div&#38;gt;&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62;&#38;lt;b&#38;gt;Definition List tag:&#38;lt;/b&#38;gt;&#60;br /&#62;
&#60;pre&#62;&#60;code&#62;&#38;lt;dd id=&#38;quot;publisher&#38;quot; class=&#38;quot;field&#38;quot;&#38;gt;
&#38;lt;dt&#38;gt;Publisher&#38;lt;/dt&#38;gt;
&#38;lt;dl&#38;gt;Minnesota Historical Society&#38;lt;/dl&#38;gt;
&#38;lt;/dd&#38;gt;&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62;What are others thoughts on this?
&#60;/p&#62;</description>
</item>
<item>
<title>SheilaBrennan on "adding more metadata fields?"</title>
<link>http://omeka.org/forums/topic/adding-more-metadata-fields#post-542</link>
<pubDate>Thu, 17 Jul 2008 18:42:53 +0000</pubDate>
<dc:creator>SheilaBrennan</dc:creator>
<guid isPermaLink="false">542@http://omeka.org/forums/</guid>
<description>&#60;p&#62;Hi Kif, &#60;/p&#62;
&#60;p&#62;You may add fields to any of the item types. &#60;/p&#62;
&#60;p&#62;The new release will offer a complete complement of extensible DCMI fields, so if you are looking for the few DC fields we did not include, just hang on until the fall when all possible DC fields will be available for the filling. &#60;/p&#62;
&#60;p&#62;If you are interested in adding new metafields now, you can see the Codex: &#60;a href=&#34;http://omeka.org/codex/Customizing_Item_Types_and_Metafields;&#34; rel=&#34;nofollow&#34;&#62;http://omeka.org/codex/Customizing_Item_Types_and_Metafields;&#60;/a&#62;&#60;br /&#62;
or listen to a recent screencast that demonstrates how to edit an item type to add, edit, or delete fields: &#60;a href=&#34;http://omeka.org/codex/Edit_an_Item_Type.&#34; rel=&#34;nofollow&#34;&#62;http://omeka.org/codex/Edit_an_Item_Type.&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;Sheila
&#60;/p&#62;</description>
</item>
<item>
<title>kif on "adding more metadata fields?"</title>
<link>http://omeka.org/forums/topic/adding-more-metadata-fields#post-541</link>
<pubDate>Thu, 17 Jul 2008 15:23:40 +0000</pubDate>
<dc:creator>kif</dc:creator>
<guid isPermaLink="false">541@http://omeka.org/forums/</guid>
<description>&#60;p&#62;Is it possible to add more metadata fields in addition to the set of default Dublin Core fields that are available? I've been looking through the website and haven't found an answer. Thanks!
&#60;/p&#62;</description>
</item>
<item>
<title>mem on "Language descriptors"</title>
<link>http://omeka.org/forums/topic/language-descriptors#post-538</link>
<pubDate>Tue, 15 Jul 2008 19:55:09 +0000</pubDate>
<dc:creator>mem</dc:creator>
<guid isPermaLink="false">538@http://omeka.org/forums/</guid>
<description>&#60;p&#62;Thanks. That was easy enough.
&#60;/p&#62;</description>
</item>
<item>
<title>KrisKelly on "Language descriptors"</title>
<link>http://omeka.org/forums/topic/language-descriptors#post-535</link>
<pubDate>Tue, 15 Jul 2008 14:29:38 +0000</pubDate>
<dc:creator>KrisKelly</dc:creator>
<guid isPermaLink="false">535@http://omeka.org/forums/</guid>
<description>&#60;p&#62;At the moment, you should be able to just edit the HTML for that form element in order to make it display the languages you want.  That file is located at admin/themes/default/items/form.php in your Omeka installation.  Keep in mind that this will be changing in the upcoming version of the software, but for now that is the easiest way.
&#60;/p&#62;</description>
</item>
<item>
<title>mem on "Language descriptors"</title>
<link>http://omeka.org/forums/topic/language-descriptors#post-528</link>
<pubDate>Sun, 13 Jul 2008 22:35:25 +0000</pubDate>
<dc:creator>mem</dc:creator>
<guid isPermaLink="false">528@http://omeka.org/forums/</guid>
<description>&#60;p&#62;On the data-entry page for core metadata describing items, the language field is entered by a drop-down box listing a half-dozen languages. Short of editing the database directly, is there any means of indicating languages other than the six supplied?
&#60;/p&#62;</description>
</item>
<item>
<title>TomScheinfeldt on "Associating Metadata With Batch Uploaded Files"</title>
<link>http://omeka.org/forums/topic/associating-metadata-with-batch-uploaded-files#post-347</link>
<pubDate>Sun, 13 Apr 2008 20:44:21 +0000</pubDate>
<dc:creator>TomScheinfeldt</dc:creator>
<guid isPermaLink="false">347@http://omeka.org/forums/</guid>
<description>&#60;p&#62;Hi bethnicol --&#60;/p&#62;
&#60;p&#62;In addition to a CSV importer and the generalized OAI-PMH harvester (we're still too deep in research and development to provide any documentation), we are working towards a specialized a set of CONTENTdm migration tools.  We cannot provide a firm date for when these tools will be ready, but they are high on our list of priorities for the spring and early summer.  We will make an announcement as soon as a beta version is ready.&#60;/p&#62;
&#60;p&#62;Thanks for using Omeka and letting us know how you're making out.&#60;/p&#62;
&#60;p&#62;Tom
&#60;/p&#62;</description>
</item>
<item>
<title>bethnicol on "Associating Metadata With Batch Uploaded Files"</title>
<link>http://omeka.org/forums/topic/associating-metadata-with-batch-uploaded-files#post-345</link>
<pubDate>Sat, 12 Apr 2008 23:12:03 +0000</pubDate>
<dc:creator>bethnicol</dc:creator>
<guid isPermaLink="false">345@http://omeka.org/forums/</guid>
<description>&#60;p&#62;I too am interested in the possibility of batch uploading at least image files and associated metadata. So, I would second Jsafley's comments. In my case, I am already a CONTENTdm user, but the presentation interface for Omeka makes is very attractive. However, the process of adding metadata, one field, one item at a time would really be a painful method, IMHO.&#60;/p&#62;
&#60;p&#62;Is there documentation on how the OAI-PMH harvester is designed to function? I'm thinking that might make some sort of viable way to use my Cdm collections and frontend them with Omeka. (maybe I'm all wet here.
&#60;/p&#62;</description>
</item>
<item>
<title>KrisKelly on ""Date" metadata displayed as "Provenance""</title>
<link>http://omeka.org/forums/topic/date-metadata-displayed-as-provenance#post-336</link>
<pubDate>Fri, 11 Apr 2008 16:46:27 +0000</pubDate>
<dc:creator>KrisKelly</dc:creator>
<guid isPermaLink="false">336@http://omeka.org/forums/</guid>
<description>&#60;p&#62;Thanks for catching that.  That's a typo that accidentally propagated to both of the themes bundled in Omeka.  You can fix it by opening up the 'items/show.php' page in your theme and editing line 134 to say &#34;Date&#34; instead of &#34;Provenance&#34;.  The data is stored correctly, it's just not displayed correctly.  I put up a note to fix it in the next release.
&#60;/p&#62;</description>
</item>
<item>
<title>AJMillion on ""Date" metadata displayed as "Provenance""</title>
<link>http://omeka.org/forums/topic/date-metadata-displayed-as-provenance#post-335</link>
<pubDate>Fri, 11 Apr 2008 00:39:27 +0000</pubDate>
<dc:creator>AJMillion</dc:creator>
<guid isPermaLink="false">335@http://omeka.org/forums/</guid>
<description>&#60;p&#62;KKay,&#60;/p&#62;
&#60;p&#62;That makes a lot of sense to me. I don't have access right now but will try and check out our install too. I appreciate the feedback. People are fast here. :)
&#60;/p&#62;</description>
</item>
<item>
<title>kkay on ""Date" metadata displayed as "Provenance""</title>
<link>http://omeka.org/forums/topic/date-metadata-displayed-as-provenance#post-332</link>
<pubDate>Thu, 10 Apr 2008 23:12:22 +0000</pubDate>
<dc:creator>kkay</dc:creator>
<guid isPermaLink="false">332@http://omeka.org/forums/</guid>
<description>&#60;p&#62;Provenance is incorrectly mapped on the public site of my install as well. Data in the Date field displays instead in Provenance (though it does display the correct date).&#60;/p&#62;
&#60;p&#62;I briefly looked at the svn branch and I think the item.php file in both the themes has incorrectly duplicated Provenance as the label for the Date field.
&#60;/p&#62;</description>
</item>
<item>
<title>AJMillion on ""Date" metadata displayed as "Provenance""</title>
<link>http://omeka.org/forums/topic/date-metadata-displayed-as-provenance#post-331</link>
<pubDate>Thu, 10 Apr 2008 23:01:41 +0000</pubDate>
<dc:creator>AJMillion</dc:creator>
<guid isPermaLink="false">331@http://omeka.org/forums/</guid>
<description>&#60;p&#62;I'm not sure if this was something created to ensure the accurate use of metadata, but I cannot enter incomplete date information for photographs. For example, in the item metadata fields within the &#34;Still Image&#34; item level there are the &#34;Date&#34; and &#34;Provenance&#34; fields. To update the metadata I entered the year of the image under date and nothing else. This should still be in keeping with ISO standard format. When I look at things from the administrative display it shows the proper information. Unfortunately, when I use the end-user display it does not display date and changes the information to &#34;Provenance - [one month].&#34;&#60;/p&#62;
&#60;p&#62;Does anyone have a clue as to why it is doing this? Not all of my images have full dates and I don't want incorrect information to be displayed. Additionally, I don't want the date information displayed as &#34;Provenance,&#34; because &#34;Date&#34; is all I need. Any help would be appreciated.
&#60;/p&#62;</description>
</item>
<item>
<title>AJMillion on "Associating Metadata With Batch Uploaded Files"</title>
<link>http://omeka.org/forums/topic/associating-metadata-with-batch-uploaded-files#post-277</link>
<pubDate>Wed, 26 Mar 2008 03:48:36 +0000</pubDate>
<dc:creator>AJMillion</dc:creator>
<guid isPermaLink="false">277@http://omeka.org/forums/</guid>
<description>&#60;p&#62;Jsafley,&#60;/p&#62;
&#60;p&#62;Thanks for responding. The CSV support would be a good step, because anyone exporting/importing metadata will likely be able to convert other formats into this one. Another idea would be to enable the use of XML, but as with all of these formats I suspect the issue of precise mapping might come up.&#60;/p&#62;
&#60;p&#62;The CSV / batch idea is a good one. I used something similar last year while working on an archival project but it was much less flexible. A tech rigged it up so we could import a bunch of old files. We used the .jpg file names to associate the two prior to our uploading. It worked fine.&#60;/p&#62;
&#60;p&#62;I'm just interested in finding ways to batch process large amounts of images (to see how Omeka handles). I know it's designed to be &#34;museum like,&#34; but if the style sheets are configured correctly and images are properly arranged, then I don't see how it couldn't start to cross over into &#34;archive-land.&#34;
&#60;/p&#62;</description>
</item>
<item>
<title>jsafley on "Associating Metadata With Batch Uploaded Files"</title>
<link>http://omeka.org/forums/topic/associating-metadata-with-batch-uploaded-files#post-268</link>
<pubDate>Tue, 25 Mar 2008 13:37:05 +0000</pubDate>
<dc:creator>jsafley</dc:creator>
<guid isPermaLink="false">268@http://omeka.org/forums/</guid>
<description>&#60;p&#62;Hi AJMillion. There is currently no way to associate metadata with individual items during batch uploads, but it's a good idea and one that should be implemented. We're currently working on a CSV Import plugin that will import items from a CSV file into Omeka (although for the moment it's taking a back seat to our upcoming OAI-PMH harvester). Maybe we can somehow tie in the CSV plugin to the Dropbox plugin, which would allow simultaneous file and metadata import.&#60;/p&#62;
&#60;p&#62;In the meantime I think you're limited to using the Dropbox plugin to batch upload files and separately editing the individual items. Not quite an efficient process, but It'll get the job done. Do you have any other ideas?
&#60;/p&#62;</description>
</item>
<item>
<title>AJMillion on "Associating Metadata With Batch Uploaded Files"</title>
<link>http://omeka.org/forums/topic/associating-metadata-with-batch-uploaded-files#post-265</link>
<pubDate>Tue, 25 Mar 2008 04:23:51 +0000</pubDate>
<dc:creator>AJMillion</dc:creator>
<guid isPermaLink="false">265@http://omeka.org/forums/</guid>
<description>&#60;p&#62;I have been toying around with the Omeka dropbox plugin and would like to thank the support staff for providing it. The tool provides an easy way to batch import files; something  very useful. :) That said, I was wondering if there is a way to quickly associate metadata with batch uploads? I know that Omeka associates unique item id keys to new uploaded items (I assume this has to do with the underlying database) so associating files and information should be as simple as mapping the correct information. But, this doesn't necessarily make it easy.&#60;/p&#62;
&#60;p&#62;Anyone have a clue on this?
&#60;/p&#62;</description>
</item>

</channel>
</rss>
