Home > User manual

User manual

[under construction]

1. Omeka explained:

Omeka is easy. It is a web-based application that is made for storing, organizing and sharing digital collections, as well as for creating media-rich online exhibits.

Omeka is basically an online catalogue, based on "items" (or records in the catalogue).
Each item can be associated to one or multiple actual "file(s)", but an "item" can exist without files too.
Finally, each "item" can be part of one or more "collections".

This catalogue can be browsed and searched according to the information contained in the description fields of each "item".

Therefore, it is important to use a simple but rigorous standard when preparing the description (or "metadata") of each record. This standard is "Dublin Core". 

Technically, the information of each "item" as well as the thumbnails of the files are stored on the Omeka server, which can be accessed only by MODSCAPES team members. The "Files", instead, are stored on a distinct server, which can be accessed only by Modscapes Omeka application onlt (nad by webmaster). It is not possible to access (view, delete, download) "files" if you are not connected to Modscapes' Omeka at the same time. No one with the link of the file can actually access it otherwise.

COLLECTION TREE NEEDED

+ NUMBER OF ITEMS REQUESTED

+ NAMING OF CSV FILES + dropbox files

2. Dublin Core explained:

Dublin Core is easy. It is a standard for organizing information related to an item.
This information is called "metadata".

The main item types we are going to use are:

  1. Text
  2. Still Image
  3. Map [raster-based]
  4. Map [vecotr-based]
  5. Sound
  6. Moving Image
  7. Physical Object
  8. Interactive Resource
  9. Event
  10. Dataset
  11. Software
  12. Collection

See for details:

  • TEXT
    A resource consisting primarily of words for reading: books, letters, dissertations, poems, newspapers, articles, conference proceedings, interview transcript. Note that facsimiles or images of texts are still of the genre Text)
  • STILL IMAGE
    A static visual representation other than text: images and photographs of physical objects, paintings, prints, drawings, other images and graphics, diagrams, musical notation, graphic designs. May include both electronic and physical representations. Recommended best practice is to assign the type Text to images of textual materials).
  • - MAP [RASTER-BASED] (cartographic representations of an existing, planned or desired physical reality: blueprints, topographic, cadastral, geographic, military, geologic maps. Typical formats include .jpg, .jpeg, .tiff, .png, .bmp, [also .sid, .mrsid [lizardtech])
  • - MAP [VECTOR-BASED] (GIS or CAD cartographic representations of an existing, planned or desired physical reality (use "Dataset" for the associated attribute tables). Examples include topographic, cadastral, geographic, military, geologic maps).
  • - MOVING IMAGE (A series of visual representations imparting an impression of motion when shown in succession: animations, movies, television programs, videos, moving pictures, film, zoetropes, or visual output from a simulation).
  • - SOUND (A resource primarily intended to be heard: music playback file format, an audio compact disc, and recorded speech or sounds)
  • - PHYSICAL OBJECT (An inanimate, three-dimensional object, substance, PLACE or PERSON, model or maquette. Note that digital representations of, or surrogates for, these objects should use Image, Text or one of the other types).
  • - INTERACTIVE RESOURCE (A resource requiring interaction from the user to be understood, executed, or experienced: DVD, website, online forms, applets, multimedia learning objects, virtual reality environments)
  • - DATASET (Data encoded in a defined structure: lists, tables, and databases... A dataset may be useful for direct machine processing).
  • - EVENT (A non-persistent, time-based occurrence. Provide information about purpose, location, duration, and responsible agents associated with the event: exhibition, webcast, conference, workshop, open day, performance, battle, trial, wedding, tea party, conflagration)
  • - COLLECTION (A collection is described as a group; its parts may also be separately described.)
  • - SOFTWARE (A computer program in source or compiled form)

A number of fields is used to organize an item's metadata.
Dublin Core provides a basic set of 15 fields, plus more additional fields. Potentially, a system can include an infinite number of customized fields.
This is especially useful because Dublin Core provides very generic, and sometimes ambiguous fields.
Nevertheless, to simplify uploading, updating and maintaining our database, and to allow an easy interoperability with other systems, we are going to use exclusively Dublin Core fields and in a limited number (17 fields):

  1. Title 
  2. Alternative Title 
  3. Type 
  4. Creator 
  5. Contributor 
  6. Is Part Of 
  7. Publisher 
  8. Date 
  9. Identifier [ie. Resource Identifier]
  10. Subject [ie. Subject and Keywords]
  11. Description 
  12. Coverage 
  13. Format 
  14. Language 
  15. Bibliographic Citation 
  16. Is Referenced By 
  17. Rights [ie. Rights Management]

Out of these 17 fields, only a few are strictly necessary to allow an "item" to be created, and only the 9 ones in bold may be really important for our case. 

3. CSV Import:

http://omeka.org/classic/docs/Plugins/CSV_Import/

consider installing CsvImport+ https://github.com/Daniel-KM/CsvImportPlus
See tutorial: https://drive.google.com/file/d/0B7yRUzBulzurQTZWUXY1U29sVWM/view?usp=sharing
See help here: CSV Import : what path to local files?

Short video tutorial: https://vimeo.com/104014678

First thing is to define the collection to which the items will be added.
Go to Collection and create a new one if needed.

Second, select the "Type

Possibility to directly import files from URL!!!

How to undo an import?

How to update?

Undoing a CSV import!!

File size limit for CSV, for URL files, and for Dropbox files? 

Template CSV file

  1. Open a blank file in Excell
  2. Import the template CSV file
    • In "File" menu, select "Import", then "Select file" in the file explorer window, then click "Get data"
    • A "Text Import Wizard" opens
    • Tick the "Delimited" box and select "File origin = Unicode (UTF-8)
    • Click "Next" to move to page 2 of "Text Import Wizard"
    • Tick the "Comma" box and uncheck all other "delimiters"
    • Select "Text qualifier = quotation mark"
    • Click "Next" to move to page 3 of "Text Import Wizard"
    • Select "Column Data format = General"
    • Click on the "Advanced button"
    • Select "Decimal separator = comma"
    • Select "Thousands separator = dot" and click the "Ok" button to close the "Advanced Text Import Settings" window
    • Back to page " of the "Tet Import Wizard", click the "Finish" button
    • A last window pops up, asking "Where do you want to to put the data?" > select the very first cell "=$A$1" and click "Ok"

 

4. Dropbox

File size limit?

The Dropbox plugin in Omeka allows users to batch (massively) upload a large quantity of files at one time. Current settings allow to upload up to 512MB of files (in total) at a time.

Once files are uploaded, you may create unique items from each file, and you may associate numerous files with pre-existing items.
The recommended behaviour is to use the CSV import tool, to create the records for each file you want to upload, then to upload such files through Dropbox. Once both the CSV table and the files have been uploaded, the list of files will appear in the "files tab" when adding or editing items, and under the Dropbox tab.

Once an uploaded file has been associated to a record, it disappears from the available "Dropbox" files, and is automatically stored in the Omeka's disk server.

There are several ways to upload files to Omeka's Dropbox folder:

A. [recommended] Using an FTP client application (such as Filezilla for Mac or Windows)

Launch your local FTP client application, then connect to the server using the following credentials:

  • FTP server = ftp.modscapes-tools.eu
  • FTP server port = 21
  • Username = XXX@omeka.modscapes-tools.eu
    replace XXX with the same user as the one used for Modscapes website
  • Password = same as for Modscapes website

Now upload your files to the folder (max. 512MB at a time).
Do not upload additional folders with files in it. All files must uploaded in the same folder.

Once uploaded is completed, log out, go back to Omeka, and start associating uploaded files to records.

B. Using modscapes' file uploader system (Owncloud)

Open a browser window, and navigate to https://intranet.modscapes-tools.eu/Owncloud/index.php/login

Log in with the same User and Password as the one used for Modscapes website.

You now see a folder entitled "Upload your Omeka files WITHIN this folder"

Double clik on this folder, and drag and drop your files to the folder (max. 512MB at a time).
Do not upload additional folders with files in it. All files must uploaded in the same folder.

Once uploaded is completed, log out, go back to Omeka, and start associating uploaded files to records.

C. [not recommended] Using a web-based FTP client

Open a browser window, and navigate to https://www.onlineftp.ch, then connect to the server using the following credentials:

  • FTP server = ftp.modscapes-tools.eu
  • FTP server port = 21
  • Username = XXX@omeka.modscapes-tools.eu
    replace XXX with the same user as the one used for Modscapes website
  • Password = same as for Modscapes website

Now upload your files to the folder (max. 512MB at a time).
Do not upload additional folders with files in it. All files must uploaded in the same folder.

Once uploaded is completed, log out, go back to Omeka, and start associating uploaded files to records.

 

Working with Zotero:

http://omeka.org/classic/docs/Plugins/ZoteroImport/

DON'T upload zipped files or folders!!!
MAKE SURE all files have unequivocal filenames (to avoid having someone else upoading another file with same name!!!)
DON'T upload more than 512MB at a time (all files together).

CSV export:

- for an item: go to item's details, and you'll see a "csv" link among the available output formats. Typical format of link is:
https://omeka.modscapes-tools.eu/items/show/XXX?output=csv
where XXX is the item's #

- for a collection: go to item's details, and you'll see a "csv" link among the available output formats. Typical format of link is:
https://omeka.modscapes-tools.eu/items/browse?collection=XXX?output=csv
where XXX is the collection's #

 

Mapping with Neatline

http://docs.neatline.org/map-tab-importing-svg.html

http://docs.neatline.org/working-with-the-text-widget.html

http://docs.neatline.org/working-with-the-simile-timeline-widget.html

http://docs.neatline.org/working-with-the-waypoints-plugin.html

NeatlineFEATURES: not really convincing: in add item page, it adds a map to DC:Coverage field, where one can draw figures, but such figures are used only in Neatline and not populating the DC:Coverage field
(https://github.com/scholarslab/NeatlineFeatures) 

NEATLINE uses a specific system of coordinates, different from the degree-based WGS84 commonly used in web-based geoservers (such as google's): that is EPSG 3857 (metric). So longitude/latitude coordinates need to be converted to this system.
Besides, coordinates need to be wrapped in codes:

  • always preceded by "GEOMETRYCOLLECTION("
  • always followed by the type of object "POINT(", POLYGON((" or "LINESTRING("
  • always separate long/lat coordinates with white space
  • always separate pairs of coordinates with comma
  • always concluded by the appropriated number of coordinates

EXAMPLE:

  • GEOMETRYCOLLECTION(POINT(long lat))
  • GEOMETRYCOLLECTION(POLYGON((long lat,long lat,long lat)))
  • GEOMETRYCOLLECTION(LINESTRING(long lat,long lat,long lat)
  • Multiple values: 
    • GEOMETRYCOLLECTION(POINT(long lat),POLYGON((long lat,long lat,long lat)),LINESTRING(long lat,long lat,long lat))

For the record, the Excell formula to convert decimal WPS84 coordinates into EPSG:2857 are

  • =(long*20037508,34/180)
  • =(LN(TAN((90+lat)*PI()/360))/(PI()/180))*20037508,34/180

Neatline and geolocation use a dot-delimited decimal separator

The JSON line of code is (for POINTS only):

# convert lat/long data in WKT
def latlon2wkt(lat,long) :
half_circ = 20037508.34
x = long * half_circ /180
y = math.log(math.tan((90 + lat) * math.pi / 360)) / (math.pi / 180)
y = y * half_circ / 180
return "GEOMETRYCOLLECTION(POINT("+str(x)+" "+str(y)+"))"


http://www.qgistutorials.com/de/docs/web_mapping_with_qgis2web.html

GEOLOCATION

Stored in PhP table "omeka_locations"

Access rights

Limit access to original files (for public view): https://forum.omeka.org/t/original-document-access-limitation-based-on-access-rights/1460