search

plagmada / plagmada-archives

2 stars 1 forks source link

Omeka Evaluation #14

Open truephredd opened 8 years ago

truephredd commented 8 years ago

Omeka http://omeka.org/

Critical

truephredd commented 8 years ago

Well, AFAICT, Omeka DOES tick most of our boxes. Definitely extensible. Definitely able to scale as we grow.

The questions I have about are regarding the UI for casual users just wanting to browse and also the ease of use of the framework for internal volunteers & the support folks (hi @riverfr0zen)

@kwhite2 - Can you say anything about any experiences you have regarding ease of use for users coming to Omeka sites?

truephredd commented 8 years ago

@riverfr0zen - Thoughts on the stack?:

Omeka includes:

Zend Framework getID3 jQuery jQuery UI TinyMCE Silk Icons

kwhite2 commented 8 years ago

All,

Omeka is EXTEREMELY easy to use from both the external user and internal volunteer standpoint, which is another reason that I suggested it. With some properly written documentation (by me), and the online information already available in the Omeka Codex, those two use cases should not be a problem. I'd be happy to run a Google Hangout to run folks through the basics some time.

HOWEVER, the interface itself is a bit clunky on the back end. Every time you perform a task, if you want to utilize a different function, you have to go all the way back out to the Dashboard. Some of the sub-functions are not obvious within the menu structure of a given function, so documentation is going to be really important for volunteers on the back end.

The basic metadata schema is Dublin Core (DC), which is extensible. There is also a DC/EAD crosswalk, which means that we can give metadata to the Strong Museum in their preferred format, though it will take some massaging. It should be easy to set up an online form to facilitate this task.

Krista

Krista White Digital Humanities Librarian, Head Media Services John Cotton Dana Library Rutgers-The State University of New Jersey Newark, New Jersey 07102 (973)353-5913

"Wòch nan dlo pa konnen doulè wòch nan solèy." (The rock in the water does not know the pain of the rock in the sun)

----- Original Message ----- From: "Phredd Groves" notifications@github.com To: "plagmada/plagmada-archives" plagmada-archives@noreply.github.com Cc: "kwhite2" kwhite2@rutgers.edu, "Mention" mention@noreply.github.com Sent: Wednesday, August 3, 2016 11:46:34 PM Subject: Re: [plagmada/plagmada-archives] Omeka Evaluation (#14)

Well, AFAICT, Omeka DOES tick most of our boxes. Definitely extensible. Definitely able to scale as we grow.

The questions I have about are regarding the UI for casual users just wanting to browse and also the ease of use of the framework for internal volunteers & the support folks (hi @riverfr0zen)

@kwhite2 - Can you say anything about any experiences you have regarding ease of use for users coming to Omeka sites?

You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/plagmada/plagmada-archives/issues/14#issuecomment-237445032

kwhite2 commented 8 years ago

Here is a workshop I co-wrote and presented on Omeka with some colleagues at work. Materials might prove useful for folks here as we consider which platform to use:

https://drive.google.com/folderview?id=0B_Mn4KFMciSWSi1sV3BSUU1lRHM&usp=sharing

Krista

----- Original Message ----- From: "Krista White" kwhite2@rulmail.rutgers.edu To: "plagmada/plagmada-archives" reply@reply.github.com Cc: "plagmada/plagmada-archives" plagmada-archives@noreply.github.com, "kwhite2" kwhite2@rutgers.edu, "Mention" mention@noreply.github.com Sent: Friday, August 5, 2016 12:41:09 PM Subject: Re: [plagmada/plagmada-archives] Omeka Evaluation (#14)

All,

Omeka is EXTEREMELY easy to use from both the external user and internal volunteer standpoint, which is another reason that I suggested it. With some properly written documentation (by me), and the online information already available in the Omeka Codex, those two use cases should not be a problem. I'd be happy to run a Google Hangout to run folks through the basics some time.

HOWEVER, the interface itself is a bit clunky on the back end. Every time you perform a task, if you want to utilize a different function, you have to go all the way back out to the Dashboard. Some of the sub-functions are not obvious within the menu structure of a given function, so documentation is going to be really important for volunteers on the back end.

The basic metadata schema is Dublin Core (DC), which is extensible. There is also a DC/EAD crosswalk, which means that we can give metadata to the Strong Museum in their preferred format, though it will take some massaging. It should be easy to set up an online form to facilitate this task.

Krista

Krista White Digital Humanities Librarian, Head Media Services John Cotton Dana Library Rutgers-The State University of New Jersey Newark, New Jersey 07102 (973)353-5913

"Wòch nan dlo pa konnen doulè wòch nan solèy." (The rock in the water does not know the pain of the rock in the sun)

----- Original Message ----- From: "Phredd Groves" notifications@github.com To: "plagmada/plagmada-archives" plagmada-archives@noreply.github.com Cc: "kwhite2" kwhite2@rutgers.edu, "Mention" mention@noreply.github.com Sent: Wednesday, August 3, 2016 11:46:34 PM Subject: Re: [plagmada/plagmada-archives] Omeka Evaluation (#14)

Well, AFAICT, Omeka DOES tick most of our boxes. Definitely extensible. Definitely able to scale as we grow.

The questions I have about are regarding the UI for casual users just wanting to browse and also the ease of use of the framework for internal volunteers & the support folks (hi @riverfr0zen)

@kwhite2 - Can you say anything about any experiences you have regarding ease of use for users coming to Omeka sites?

You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/plagmada/plagmada-archives/issues/14#issuecomment-237445032

riverfr0zen commented 8 years ago

Assigning to self to install plugins as listed by @kwhite2