Difference between revisions of "Installing Omeka for CEDEUS"

From stgo
Jump to: navigation, search
(→‎Setup of Omeka VM)
 
(15 intermediate revisions by one user not shown)
Line 5: Line 5:
 
=== Setup of Omeka VM ===
 
=== Setup of Omeka VM ===
 
==== Setup of VM based on Ubuntu 1404 VM ====
 
==== Setup of VM based on Ubuntu 1404 VM ====
−
# copying basicubuntu1404.vdi file and renaming to omeka.vdi
+
# copying basicubuntu1404.vdi file and renaming to omeka_ubuntu.vdi (note, accidentally I i used the nominatim VM disc, so I copied and renamed the VDI file to omeka_w_nominatim.vdi)
 
# creating the omeka VM on CedeusDB (ip.18):
 
# creating the omeka VM on CedeusDB (ip.18):
 
#* <code>VBoxManage createvm --name omeka --ostype Ubuntu_64 --register</code>
 
#* <code>VBoxManage createvm --name omeka --ostype Ubuntu_64 --register</code>
Line 12: Line 12:
 
#* <code>VBoxManage modifyvm omeka --nic1 nat</code>
 
#* <code>VBoxManage modifyvm omeka --nic1 nat</code>
 
#* <code>VBoxManage storagectl omeka --name "SATA Controller" --add sata --controller IntelAhci</code>
 
#* <code>VBoxManage storagectl omeka --name "SATA Controller" --add sata --controller IntelAhci</code>
−
#* <code>VBoxManage internalcommands sethduuid omeka.vdi</code>
+
#* <code>VBoxManage internalcommands sethduuid omeka_w_nominatim.vdi</code>
−
#* <code>VBoxManage storageattach "omeka" --storagectl "SATA Controller" --port 0 --device 0 --type hdd --medium omeka.vdi</code>
+
#* <code>VBoxManage storageattach "omeka" --storagectl "SATA Controller" --port 0 --device 0 --type hdd --medium omeka_w_nominatim.vdi</code>
 
#* <code>VBoxManage storagectl omeka --name "IDE Controller" --add ide --controller PIIX4</code>
 
#* <code>VBoxManage storagectl omeka --name "IDE Controller" --add ide --controller PIIX4</code>
 
#* <code>VBoxManage modifyvm omeka --natpf1 "ssh,tcp,,20022,,22"</code>
 
#* <code>VBoxManage modifyvm omeka --natpf1 "ssh,tcp,,20022,,22"</code>
 
#* <code>VBoxManage modifyvm omeka --natpf1 "apache,tcp,,20080,,80"</code>
 
#* <code>VBoxManage modifyvm omeka --natpf1 "apache,tcp,,20080,,80"</code>
 
#* <code>VBoxManage modifyvm omeka --vrdeport 7764</code>
 
#* <code>VBoxManage modifyvm omeka --vrdeport 7764</code>
 +
# start VM and change the computers name:
 
#* <code>VBoxHeadless -s omeka --vrde on &</code>
 
#* <code>VBoxHeadless -s omeka --vrde on &</code>
 +
#* change computers name in /etc/hosts and /etc/hostname to omeka
 +
#* restarting Apache gives the error message: "apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 ..."
 +
#:: => solve this by adding ServerName nominatim as the last line in /etc/apache2/apache2.conf file
 +
#* add additional users
 +
 +
==== Adjustments to Apache config file ====
 +
changes to ''/etc/apache2/sites-available/000-default.conf''
 +
 +
<VirtualHost *:80 146.155.17.18:20022>
 +
 +
        #ServerName www.example.com
 +
        ServerName cedeuspubs.geosteiniger.cl
 +
        ServerAdmin webmaster@localhost
 +
        DocumentRoot /var/www/html
 +
 +
        Redirect /pubs http://cedeuspubs.geosteiniger.cl/omeka/
 +
 +
        ErrorLog ${APACHE_LOG_DIR}/error.log
 +
        CustomLog ${APACHE_LOG_DIR}/access.log combined
 +
 +
        <Directory "/var/www/html/nominatim/">
 +
          Options FollowSymLinks MultiViews
 +
          AddType text/html  .php
 +
        </Directory>
 +
 +
        <Directory /var/www/>
 +
          Options Indexes FollowSymLinks MultiViews
 +
          AllowOverride All
 +
          Order allow,deny
 +
          allow from all
 +
        </Directory>
 +
 +
        <Directory "/var/www/html">
 +
          AllowOverride All
 +
        </Directory>
 +
 +
        <Directory "/var/www/html/omeka">
 +
          AllowOverride All
 +
        </Directory>
 +
 +
        RedirectMatch ^/$ /omeka/
 +
</VirtualHost>
 +
 +
== Notes on Omeka ==
 +
 +
=== starting to use Omeka ===
 +
* Make a plan on how it should be used first, as described here: http://omeka.org/codex/Site_Planning_Tips
 +
* items and collection (formed of items) are the basic elements:
 +
** items: http://omeka.org/codex/Managing_Items_2.0
 +
** collections: http://omeka.org/codex/Managing_Collections_2.0
 +
 +
=== public vs private items ===
 +
see:
 +
* http://omeka.org/forums/topic/issues-with-contributor-user-role
 +
* plugins:
 +
** http://omeka.org/codex/Plugins/Contribution_2.0 and, corresponding "guest user plugin":
 +
** http://omeka.org/codex/Plugins/GuestUser_2.0
 +
* and, perhaps ??? for (filter) plugin development: http://omeka.org/forums/topic/ability-to-set-files-to-public-or-private
 +
 +
=== changing file upload size ===
 +
 +
Omeka uses the PhP default settings. So how to do that see http://www.cyberciti.biz/faq/linux-unix-apache-increase-php-upload-limit/
 +
 +
* open ''/etc/php5/apache2/php.ini''
 +
* set the following variables:
 +
** <code>upload_max_filesize</code> (I chose 60MB)
 +
** <code>memory_limit</code> (I chose 128MB)
 +
** <code>post_max_size</code> (I chose 80MB)
 +
 +
=== Zotero and Omeka ===
 +
 +
Omeka can import data from a Zotero Group, so...
 +
* I created a new Zotero group with my account (public visible, but private membership): https://www.zotero.org/groups/observatorio_cedeus
 +
* Then I generated an API access key for this group (from my Zotero home/account page) that allows read access only to this new Observatory group
 +
* Then I copied the Atom Feed URL to the Omeka Form, including the Zotero Access key
 +
* Then I was able to select/and access stuff stored in the new group library (Ebrhaims 2015 IJGI paper) and importing it as item into Omeka.
 +
*: => Note, the '''pdf''' of the publication was '''not attached'''! I added the pdf file later manually from my desktop using ''Item'' > ''Editar'' > ''Archivos''.
 +
 +
= Solution for hdd problem =
 +
 +
for the problem '''Error: failed to start machine. Error message: UUID {64c8360e-8ce4-48de-844a-f3182a6815f1} of the medium '/home/ssteinig/omeka_w_nominatim.vdi' does not match the value {b7f765c4-c84e-4a34-87ac-c0fda5a6bdcf} stored in the media registry ('/home/ssteinig/.config/VirtualBox/VirtualBox.xml')'''
 +
 +
<source lang="bash">
 +
VBoxManage storageattach "omeka2" --storagectl "SATA Controller" --port 0 --device 0 --type hdd --medium none
 +
VBoxManage closemedium disk b7f765c4-c84e-4a34-87ac-c0fda5a6bdcf
 +
VBoxManage storageattach "omeka2" --storagectl "SATA Controller" --port 0 --device 0 --type hdd --medium omeka_w_nominatim.vdi
 +
</source>

Latest revision as of 16:51, 7 November 2016

>> return to Cedeus IDE

Installing Omeka

Setup of Omeka VM

Setup of VM based on Ubuntu 1404 VM

  1. copying basicubuntu1404.vdi file and renaming to omeka_ubuntu.vdi (note, accidentally I i used the nominatim VM disc, so I copied and renamed the VDI file to omeka_w_nominatim.vdi)
  2. creating the omeka VM on CedeusDB (ip.18):
    • VBoxManage createvm --name omeka --ostype Ubuntu_64 --register
    • VBoxManage modifyvm omeka --memory 8096
    • VBoxManage modifyvm omeka --cpus 4
    • VBoxManage modifyvm omeka --nic1 nat
    • VBoxManage storagectl omeka --name "SATA Controller" --add sata --controller IntelAhci
    • VBoxManage internalcommands sethduuid omeka_w_nominatim.vdi
    • VBoxManage storageattach "omeka" --storagectl "SATA Controller" --port 0 --device 0 --type hdd --medium omeka_w_nominatim.vdi
    • VBoxManage storagectl omeka --name "IDE Controller" --add ide --controller PIIX4
    • VBoxManage modifyvm omeka --natpf1 "ssh,tcp,,20022,,22"
    • VBoxManage modifyvm omeka --natpf1 "apache,tcp,,20080,,80"
    • VBoxManage modifyvm omeka --vrdeport 7764
  3. start VM and change the computers name:
    • VBoxHeadless -s omeka --vrde on &
    • change computers name in /etc/hosts and /etc/hostname to omeka
    • restarting Apache gives the error message: "apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 ..."
    => solve this by adding ServerName nominatim as the last line in /etc/apache2/apache2.conf file
    • add additional users

Adjustments to Apache config file

changes to /etc/apache2/sites-available/000-default.conf 

<VirtualHost *:80 146.155.17.18:20022>

       #ServerName www.example.com
       ServerName cedeuspubs.geosteiniger.cl
       ServerAdmin webmaster@localhost
       DocumentRoot /var/www/html

       Redirect /pubs http://cedeuspubs.geosteiniger.cl/omeka/

       ErrorLog ${APACHE_LOG_DIR}/error.log
       CustomLog ${APACHE_LOG_DIR}/access.log combined

       <Directory "/var/www/html/nominatim/">
          Options FollowSymLinks MultiViews
          AddType text/html   .php
       </Directory>

       <Directory /var/www/>
          Options Indexes FollowSymLinks MultiViews
          AllowOverride All
          Order allow,deny
          allow from all
       </Directory>

       <Directory "/var/www/html">
          AllowOverride All
       </Directory>

       <Directory "/var/www/html/omeka">
          AllowOverride All
       </Directory>

       RedirectMatch ^/$ /omeka/
</VirtualHost>

Notes on Omeka

starting to use Omeka

public vs private items

see:

changing file upload size

Omeka uses the PhP default settings. So how to do that see http://www.cyberciti.biz/faq/linux-unix-apache-increase-php-upload-limit/

  • open /etc/php5/apache2/php.ini
  • set the following variables:
    • upload_max_filesize (I chose 60MB)
    • memory_limit (I chose 128MB)
    • post_max_size (I chose 80MB)

Zotero and Omeka

Omeka can import data from a Zotero Group, so...

  • I created a new Zotero group with my account (public visible, but private membership): https://www.zotero.org/groups/observatorio_cedeus
  • Then I generated an API access key for this group (from my Zotero home/account page) that allows read access only to this new Observatory group
  • Then I copied the Atom Feed URL to the Omeka Form, including the Zotero Access key
  • Then I was able to select/and access stuff stored in the new group library (Ebrhaims 2015 IJGI paper) and importing it as item into Omeka.
    => Note, the pdf of the publication was not attached! I added the pdf file later manually from my desktop using Item > Editar > Archivos.

Solution for hdd problem

for the problem Error: failed to start machine. Error message: UUID {64c8360e-8ce4-48de-844a-f3182a6815f1} of the medium '/home/ssteinig/omeka_w_nominatim.vdi' does not match the value {b7f765c4-c84e-4a34-87ac-c0fda5a6bdcf} stored in the media registry ('/home/ssteinig/.config/VirtualBox/VirtualBox.xml') 

VBoxManage storageattach "omeka2" --storagectl "SATA Controller" --port 0 --device 0 --type hdd --medium none
VBoxManage closemedium disk b7f765c4-c84e-4a34-87ac-c0fda5a6bdcf
VBoxManage storageattach "omeka2" --storagectl "SATA Controller" --port 0 --device 0 --type hdd --medium omeka_w_nominatim.vdi
Retrieved from "http://wiki.geosteiniger.cl/mediawiki-1.22.7/index.php?title=Installing_Omeka_for_CEDEUS&oldid=2076"