However, that module is not available in the sandbox installation.
Since “date” types are such a fundamentally basic thing in collection-management, I was wondering why that is so?
I totally get it that the sandbox is a demo for “the core”.
Therefore I was surprised that “date handling as timestamp(numerical)” does not seem to be a core functionality.
How is it in the production installation you know?
Is date nowadays rather entered as strings than “dates”?
It really depends on the needs of the users and the projects. Numeric Data Types is the module that makes date and time data types possible, and there are others that are available via modules (controlled vocabs, etc). The idea is that data types are extensible and can be locked in as needed.
I, personally, almost always add Numeric Data Types to an initial installation, but I’m sure there are many users who do not.
The more I’m reading, the more I think I mistook Omeka for a collection-management system (or “catalog”) with web-publishing option.
But it seems that it’s a good web-publishing tool with professional collections in mind: which would require a collection-management-system/catalog next to it, for “working” with the data like we do in the archives.
People do use it for a range of collections management needs – in some cases hiding fields so that they are only visible administratively. But, the system does not yet have a set of modules designed to support the administrative management of physical collections.
