<?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 Forum: Data Migration, Import/Export, Interoperability</title>
<link>http://omeka.org/forums/</link>
<description>Forums Forum: Data Migration, Import/Export, Interoperability</description>
<language>en</language>
<pubDate>Wed, 15 Oct 2008 21:56:54 +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>KrisKelly on "Remote procedure calls (RPC)"</title>
<link>http://omeka.org/forums/topic/remote-procedure-calls-rpc#post-624</link>
<pubDate>Fri, 12 Sep 2008 14:31:38 +0000</pubDate>
<dc:creator>KrisKelly</dc:creator>
<guid isPermaLink="false">624@http://omeka.org/forums/</guid>
<description>&#60;p&#62;We don't have RPC access built in to Omeka, but that could be a consideration for future versions.  IMO it would be better to have token-based authentication and modify data through a RESTful interface.  The best option would be to have a plugin that introduces either kind of API, but I'm not sure what would be involved so my guess is that there would need to be more work on the plugin API before that would be a possibility.
&#60;/p&#62;</description>
</item>
<item>
<title>Xilon on "Remote procedure calls (RPC)"</title>
<link>http://omeka.org/forums/topic/remote-procedure-calls-rpc#post-617</link>
<pubDate>Thu, 04 Sep 2008 08:32:15 +0000</pubDate>
<dc:creator>Xilon</dc:creator>
<guid isPermaLink="false">617@http://omeka.org/forums/</guid>
<description>&#60;p&#62;Is there any support in Omeka for RPC, or any way to access and possibly modify information in the database, without direct access to the database?&#60;/p&#62;
&#60;p&#62;This would be a great way for 3rd party application to interact with Omeka servers.
&#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>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>KrisKelly on "Omeka Upgrades"</title>
<link>http://omeka.org/forums/topic/omeka-upgrades#post-501</link>
<pubDate>Fri, 27 Jun 2008 23:58:40 +0000</pubDate>
<dc:creator>KrisKelly</dc:creator>
<guid isPermaLink="false">501@http://omeka.org/forums/</guid>
<description>&#60;p&#62;Hi, the general process for upgrading will be the same as before.  People who are upgrading will move their config files and archive directory from the old omeka to the new one and then run a script through the administrative backend to upgrade their database.  That will be the extent of the upgrade for anyone who hasn't modified any of the PHP files in Omeka.&#60;/p&#62;
&#60;p&#62;When you say &#34;get too far along in something&#34;, do you mean changing the core of the application, or do you making extensions like themes or plugins?  If you've changed any PHP files in Omeka's code base that aren't either plugins, themes, or configuration files, chances are that your changes won't work in the new version.  It'd be best to make a list of all the things you've changed and then it will be easier to upgrade later.  &#60;/p&#62;
&#60;p&#62;Plugins and themes are a different story.  I can say with certainty that the API for Omeka's themes and plugins in the next version will be changing considerably from the current 0.9 release branch, though we haven't finalized the changes yet.  The changes in the API are necessary because we've made some pretty fundamental changes to Omeka's database, and the old themes won't work with the new database.  That said, we'll be upgrading all the themes and plugins that we've released to work with the new system, so we'll most likely have instructions on our codex as well as answering specific questions on the forums.  &#60;/p&#62;
&#60;p&#62;Hope that helps!
&#60;/p&#62;</description>
</item>
<item>
<title>AJMillion on "Omeka Upgrades"</title>
<link>http://omeka.org/forums/topic/omeka-upgrades#post-497</link>
<pubDate>Tue, 24 Jun 2008 05:30:14 +0000</pubDate>
<dc:creator>AJMillion</dc:creator>
<guid isPermaLink="false">497@http://omeka.org/forums/</guid>
<description>&#60;p&#62;Hey all. I've been back and forth on the boards lately and have another question. This time, I'm curious about upgrading Omeka. I know from version .9 to .91 all that really had to be done was replace a few files. Is this going to be the case in future versions? The reason I ask is because I don't want to get too far along in something and not be able to upgrade Omeka because &#34;x&#34; change or &#34;y&#34; change has been made.&#60;/p&#62;
&#60;p&#62;Any idea of how future upgrades will be dealt with?
&#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>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>
