Factsheet
| Resource reviewed | ||
|---|---|---|
| Title | Omeka Classic | |
| Editors
Bibliographical description of responsible personnel. Please indicate names as “forename surname”. |
Elina Leblanc | |
| URI | https://omeka.org/classic/ | |
| Publication Date
Format should be either yyyy, yyyyff. or yyyy-yyyy, e.g. 2007 or 2007-2013 |
2019 | |
| Date of last access | 18.12.2019 | |
| Reviewer | ||
|---|---|---|
| Surname | Leblanc | |
| First Name | Elina | |
| Organization | Université Grenoble Alpes | |
| Place | Grenoble | |
| elina.leblanc (at) univ-grenoble-alpes.fr | ||
| General information | ||
|---|---|---|
| Type of reviewed software
Tool: computational application to be used for accomplishing one task or a number of related tasks in the process of digital scholarly editing; Virtual Research Environment (VRE): a platform on which various tools (independent or not) are working as an integrated whole in order to perform a series of tasks or to cover the entire workflow. |
What type of software is it?
|
VRE |
| Environment/platform
operating system, e.g. for stand-alone applications; web-browser for web-based applications, web-services, and APIs; another application, i.e., a plugin |
On which platform runs the tool?
|
Operating System |
| Purpose |
For what purpose was the tool developed?
|
General purpose |
| Funding |
Which is the financial model of the tool?
|
Free |
| Maturity |
What is the development stage of the tool?
|
Release |
| Methods and implementation | ||
| Programming language(s) |
Which programming languages and technologies are used?
|
PHP |
| Reuse |
Does the tool reuse portions of other existing software?
|
 |
| Input format |
Which programming languages and technologies are used?
|
XML, XML-TEI, PDF, csv |
| Output format |
Which programming languages and technologies are used?
|
HTML |
| Encoding |
Which character encoding formats are supported?
|
unknown |
| Preprocessing |
Is a pre-processing conversion included?
|
|
| Dependencies |
Does the documentation list dependencies on other software, libraries or hardware?
|
 |
| Dependencies installation |
If yes, is the software handling the installation of dependencies during the general installation process (you don’t have to install them manually before the installation)?
|
|
| Usability, sustainability and maintainability | ||
| Documentation |
Is documentation and/or a manual available? (tool website, wiki, blog, documentation, or tutorial)
|
|
| Format of documentation |
Which format has the documentation?
|
readme, HTML |
| Sections of documentation |
Which of the following sections does the documentation contain?
|
Getting-started (installation and configuration), Step-by-step instructions, Troubleshooting, FAQ, Support section |
| Language of documentation |
In what languages is the documentation available?
|
English |
| Active Support |
Is there a method to get active support from the developer(s) or from the community?
|
|
| Type of support |
Which form of support is offered?
|
Forum, Mailing list |
| Bug/issue tracker |
Is it possible to post bugs or issue using issue tracker mechanisms?
|
|
| Build and install (personal learning curve) |
Grade how straightforward it is to build or install the tool on a supported platform:
|
Normal |
| Testing |
Is there a test suite, covering the core functionality in order to check that the tool has been correctly built or installed?
|
|
| Deployment on platforms |
On which platforms can the tool/software be deployed?
|
Linux, Mac, Windows |
| Deployment on devices |
On which devices can the tool/software be deployed?
|
Deployment on desktop, Deployment on laptop, Deployment on smartphone, Deployment on tablet |
| Deployment on browser |
If the tool is web-based: On which browsers can the tool/software be deployed?
|
Mozilla, Chrome, Safari |
| Browser plugin |
If the tool is web-based: Does the tool rely on browser plugins?
|
|
| API |
Is there an API for the tool?
|
|
| Code |
Is the source code open?
|
|
| License |
Under what license is the tool released?
|
|
| Credits |
Does the software make adequate acknowledgement and credit to the project contributors?
|
|
| Registered in software repository |
Is the tool/software registered in a software repository?
|
|
| Contributing possible |
If yes, can you contribute to the software development via the repository/development platform?
|
|
| Code Analysability |
Can the code be analyzed easily (is it structured, commented, following standards)?
|
|
| Code Extensibility |
Can the code be extended easily (because there are contribution mechanisms, attribution for changes and backward compatibility)?
|
|
| Code Reusability |
Can the code be reused easily in other contexts (because there are appropriate interfaces and/or a modular architecture)?
|
|
| Information of security/privacy |
Does the software provide sufficient information about the treatment of the data entered by the users?
|
|
| Maintenance |
Is there information available whether the tool will be supported currently and in the future?
|
|
| Citability |
Does the tool supply citation guidelines (e.g. using the Citation File Format)?
|
|
| User interaction, GUI and visualization | ||
| User group |
What kind of users are expected?
|
Researcher, Scientists, Humanists, Public |
| User interaction |
What kind of user interactions are expected?
|
Reading, Visualization |
| User Interface |
What kind of interface does the tool provide?
|
Graphical User Interface |
| Visualization |
Does the tool provide a particular visualizations (in terms of analysis) of the input and/or the output data?
|
|
| User Empowerment |
Is the user allowed to customize the functioning of the tool and the output configuration?
|
|
| Accessibility |
Does the tool provide particular features for improving accessibility, allowing „people with the widest range of characteristics and capabilities” to use it?
|
|
