Derek Hulley e65b7ddd22 Merged DEV/SWIFT to HEAD (RM)
26104: RM: Remove incomplete and unnesseary unit test
   26123: RM2 - Use APi's to create record categories within record categories
          * ALF-6422: model updated with a couple of generic contructs which should be used in the place of the DOD specific types, for example file plan, record series and record category
          * Unit test added to show very simple multi-hierarchy file plan being created manually
          * Indetifier service and implementation added.  Allows the customisation (via Spring atm) of the generation of different rm types identifiers.
          * Some refactoring for model behaviour into a single package location and spring config.
   26139: RM2: Multi-hierarchy file plan
          * Unit to show record folders being created in a multi tier file plan (relates to ALF-6446)
          * fix up issues with "setup" of record folders when created manually
          * move model related behaviour into one package
          * move tests into one package
          * fix up failing unit tests
   26296: RM: Multi-hierarchy support
          * basic API support for multi-hierarchy support ()
          * refactoring of associated unit test (plus creation of base test for future use)
          * tests for API
          * creation of DispositionService API and refactoring of RecordsManagementService accordingly
          * fallout from refactor (unit test, security interceptors, etc)
   26418: RM: Support for multi-hierarchy file plans
          * Multi-hierarchy test data generated in rm base test
          * Methods in DispositionService to create a disposition schedule and retrieve disposition schedules
          * Unit tests showing disposition schedules being correctly inherited (all the way down to record folders) 
          * Fix up fallout from about tests
          * Continuing refactor of code, moving system tests into separate package
          * See ALF-6444 (RM52 - Create a disposition schedule on a record category that isn't a leaf node of a record category hierarchy)
          * See ALF-6423 (Lookup disposition schedule up multiple category hierarchy)
   26419: RM: Remove tests that need refactoring to work within a suite.
   26569: ALF-6445 : RM53 - Update a disposition schedule on a record category that isn't a leaf node of the record category hierarchy
          * Additional methods added to Records Management Service and Disposition Service as required
          * Unit tests for above
          * Multi-hierarchy unit tests showing updates happening correctly
          * Extension of broadcast action to support multi-hier
   26634: Fix buid
   27126: ALF-6447: RM54 - Insert a record category and set disposition schedule on already established hierarchy
          * Disposition schedules can be added through out a pre existing hierarchy, so long as not disposable items are effected
          * Unit test refactoring
   27911: Records Management:
          * Major refactor of how custom properties are defined in Admin service
          * Java API to reflect all the core custom property customisation features (within existing Admin service)
          * Now any aspect or type can be "customisable" .. over kill but allows use greater flexibility when we get further down the road and custom rm models are common place ... also may eventually allow editing of custom-meta data
          * Core customisable types sprung into admin config (Record, RecordFolder)
          * Bootstrap mechanism (via spring bean) added to add additional customisable types and aspects
          * DOD model types bootstraped in as customisable (series, category)
          * Separtion of DOD model from Admin service ensured (eventually we want the DOD model to be an example on a custom RM model not a nessesary part of the RM solution)
          * Auto application of custom properties to customisable types and aspect when they are created or added 
          * Fall out through from above changes and unit tests to cover new scenarios (including refactor of exisiting admin service test into newer Rm sytle)
          * Marker aspect to indicate a record meta-data and service method 
          * Service methods to return all record meta-data aspects
          * Web scrript API from above (later to power filing UI and allow multiple record meta-data aspects to applied by user)
          * See ALF-7516 and ALF-7517


git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@28225 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
2011-06-07 10:21:20 +00:00
..
2011-06-07 10:21:20 +00:00