UNC-Libraries/Carolina-Digital-Repository — Issue #12: Refactor Container Sorting
Author: gregjan
Created: 2011-10-26 21:18:42+00:00
State: open

There is way to much code in the CDR management stack that relates to maintaining ordered lists of contents. In general the need for a certain order breaks down into two use cases:

* alphabetical - this is locale specific and better done in access (The order of the alphabet changes around the world)
* explicitly ordered elements - chapters in a book, for instance.

We can add a default sort setting to the container model, specifying how the access layer should generally present the contents. The two settings above would make sense, with one of them being the default.

This does away with alphabetizing by label text in MD_CONTENTS, a overwrought function that pulls in lots of data for little gain. Instead we can ask access or Solr to sort alphabetically for the client's locale at access time.

I'd like to fold this change into the scalable-ingest branch. Comments?