DSpace doesn't really care at this time about your data, which is just dumped into a TEXT field, as you can see here:
https://github.com/DSpace/DSpace/blob/dspace-3.1/dspace/etc/postgres/database_schema.sql#L313 Of course, there have been talks about enforcing constraints on metadata using one sort of schema or another, but this is all in a conceptual stage. The only exception I can think of is that your dates must be in the YYYY-MM-DD format (not YYYY; not YYYY-MM) if they're used in an index (by default dc.date.issued and dc.date.accessioned), otherwise sorting won't work as expected. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
