Forums » Plugins and Added Functionality

1. jge | Member

   2 months ago # | |

   My English may fail me...

   There's the possibility to upload two or more files to one "item". I think this feature could be useful to make an archive that has small jpg's for public use and big tiff's for internal / institutional use.

   For example. I have a digital image of a Dürer woodcut. It's tiff and about 15 MB. I have made an jpg of it of about 2 MB that is good enough for public viewing. So I would like to upload 1 Item (the Dürer woodcut) consisting of two images with different file formats and sizes, one small enough for public viewing, one bigger and not compressed for archival purposes. So I would like to have the possibility to make one of the files public and the other not. It seems to me that at the moment I can only decide whether the item is public (or featured) or not, not the single belonging files.

   In my scenario in the item view I get two same looking thumbnails at the end of the metadata entry. I also would like to have the opportunity to mark them as different in any way: perhaps by showing rudimentary file metadata with them. (For example: <<Picture1>> jpg, 660x480; <<picture2>> tiff, 1320x960).

2. SheilaBrennan | Administrator

   2 months ago # | |

   Hello jge,

   Thank you for your suggestion about being able to make some files public and others not within the same item.

   While Omeka may certainly be used as a collections management system its primary goal is for making archives and exhibits available to the public, and so we weren't thinking about needing a function to keep a high-quality image private while making a low-res image available within the same item.

   We will certainly throw this idea around at a team meeting.

   Thanks,
   Sheila

3. jge | Member

   2 months ago # | |

   Thank you for considering it.

   Please do handle my second suggestion independent from this: even if I make all the different files of the same image public I would like to give the viewer the possibility to chose what he needs from the item page. Now there are exactly identical looking thumbnails of my very diffently sized jpgs. It means that a viewer has to open each file to recognize the difference between them.
   A colleague has managed to let the file names show up near the thumbnails (by throwing in some php code, I think), but this is only a less-than-ideal solution, because it puts some constrain on how the image files are to be named.
   Hhm, it dawns on me that you put in the possibility to have different files in the same item page for other reasons than the ones I would like to have them? --

   Can you tell me something about my other post concerning translation of omeka?

4. SheilaBrennan | Administrator

   2 months ago # | |

   One suggestion would be to edit the items/show page and include some text that tells visitors how to recognize the file size by your file naming convention. This would require you to be consistent with file naming, but it sounds like you are striving to do that already.

   Regarding a translation of Omeka, what exactly do you mean? Currently, Omeka can be used for many different languages and character sets. In order for the individual pages, such as items/show or an exhibit layout, to display on the public site in a different language you would have to edit those pages yourself. The same applies for the /admin pages as well.

   Here is an example of how Omeka can be used to create an exhibit in a language other than English from our recently-launched site, Gulag: Many Days, Many Lives: http://gulaghistory.org/exhibits/days-and-lives-r
   Here, only one exhibit is in Russian, but the archive could also be in Russian.

   Did I answer your question?

   Sheila

5. jge | Member

   2 months ago # | |

   Thanks again. The russian page looks good!

   Translation: Yes, I meant to show all pages in a different language: not only the public ones but the admin ones as well, for my german colleagues who are not so fluent in english. For example I have to translate the Dublin Core metadata set (or rather implement the german translation of dc that already exists). It took me a while to find the corresponding pages, so I thought it might be easier if I could get a list of files that contain translatable texts.

   And I thought that you might be interested in translations of the software in other languages, so I hoped perhaps you had already thought of a way to do that easily.

   By the way: we started with the thought that we could use the bilingual plugin. But there were difficulties. My colleague got the following entry in the error.log:

   =======================
   Type: Exception
   Date: 2008-05-29T16:39:02+0200Please provide a language when configuring Bilingual plugin!/srv/www/htdocs/omeka-0.9.1.1/plugins/Bilingual/plugin.php:89
   #0 [internal function]: BilingualPlugin->config(Array)
   #1 /srv/www/htdocs/omeka-0.9.1.1/application/libraries/plugins.php(168): call_user_func_array(Array, Array)
   #2 /srv/www/htdocs/omeka-0.9.1.1/application/libraries/plugins.php(187): PluginBroker->config('Bilingual')
   #3 /srv/www/htdocs/omeka-0.9.1.1/application/controllers/PluginsController.php(57): PluginBroker->install('Bilingual')
   #4 /srv/www/htdocs/omeka-0.9.1.1/application/libraries/Zend/Controller/Action.php(497): PluginsController->installAction()
   #5 /srv/www/htdocs/omeka-0.9.1.1/application/libraries/Zend/Controller/Dispatcher/Standard.php(237): Zend_Controller_Action->dispatch('installAction')
   #6 /srv/www/htdocs/omeka-0.9.1.1/application/libraries/Zend/Controller/Front.php(911): Zend_Controller_Dispatcher_Standard->dispatch(Object(Zend_Controller_Request_Http), Object(Zend_Controller_Response_Http))
   #7 /srv/www/htdocs/omeka-0.9.1.1/application/libraries/Omeka/Core.php(317): Zend_Controller_Front->dispatch()
   #8 /srv/www/htdocs/omeka-0.9.1.1/admin/index.php(33): Omeka_Core->dispatch()
   #9 {main}
   =======================

   He said to me that there never was a possibility to "provide a language" (as wanted in the first line above). So he does not understand the error (neither do I). Can you tell me something about it?
   Sorry that I stray of the topic...

6. SheilaBrennan | Administrator

   2 months ago # | |

   Hi,
   We do not have plans for offering translations at the moment, because we have a relatively small team working on Omeka. But that is where our Omeka community can contribute. For our sister project, Zotero, members of their user base have translated their Quick Start Guide into different languages, for instance: http://www.zotero.org/documentation/quick_start_guides_in_other_languages

   We do not have a list of all of the files with text needing translation, since there are many.
   Here are some general tips on finding files:

   * /themes/ directories contain folders holding all of the publicly displayed pages.
   * "common" folders contain header and footer files.
   * admin/themes directory contains folders that correspond to the backend pages.

   And, we are looking into the issue with the bilingual plugin.

   Sheila

RSS feed for this topic

Reply

You must log in to post.