Philly: Mike mentioned that OLE should not need to do coding, but that open source code would be provided by PENN for integration by OLE. Programming effort by OLE is minimal (< 100). Marc4j? Mechelle has requested help for spec writing
Working (Classification) spec folder at https://docs.google.com/a/kuali.org/folder/d/0B4D2uLuq2OS7ZURtV2Y3a0ZHMXc/edit
Sort Call Numbers
Includes Call number Browse for Search, but also for applying/assigning next sequential call number in Instance Editor.
Includes part of: As a data creator, I need to search the catalog by a variety of access points
I think the basic format of NLM numbers is the same, but they assign to ranges that LC does not. So I think you can use exactly the same normalization for NLM.
SuDoc is a different animal. Based on what one vendor does, I think you could split on spaces and punctuation and use alphabetic sorting on the alphabetical part, and numerical sorting ("2" comes before "10") on the numerical parts. So the numerical normalization would look similar to the padding of the LC classification parts.
 A few NLM references:
 SuDoc reference:
We are trying to use call number utils available in solrmarc.
But did not find any maven dependency for solrmarc in a public repository.
So we have installed the following jars in local maven repo and used the following dependencies in ole-utility project pom file. (not committed to SVN yet).
Please see if there are any issues with this approach.
Acceptance criteria revised by the Describe Tiger Team
test cases written and tested with most passing at the end of OLE 0.8