[ http://issues.collectionspace.org/browse/CSPACE-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

             Key: CSPACE-5615
             URL: http://issues.collectionspace.org/browse/CSPACE-5615
         Project: CollectionSpace
      Issue Type: Task
        Reporter: Megan Forbes
        Assignee: Richard Millet
        Priority: Blocker
         Fix For: v3.x

Hi all, Looking at the JIRA, it's a bit difficult to find out what is the current status of the Unified Configuration development. Have we got an idea on when it could be expected? Thank you for your answer. Best regards, Sébastien -----Oprindelig meddelelse----- Fra: Richard Millet (JIRA) [mailto:collectionspace@movingimage.us] Sendt: 17. december 2012 22:31 Til: Sébastien Brossard Emne: [JIRA] (CSPACE-5615) Design and Scope Discussion of Unified Configuration [ http://issues.collectionspace.org/browse/CSPACE-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CSPACE-5615 started by Richard Millet. > Design and Scope Discussion of Unified Configuration > ---------------------------------------------------- > > Key: CSPACE-5615 > URL: http://issues.collectionspace.org/browse/CSPACE-5615 > Project: CollectionSpace > Issue Type: Task > Reporter: Megan Forbes > Assignee: Richard Millet > Priority: Blocker > Fix For: v3.x > > > 1. Unified configuration > Problem: It is too difficult to configure CollectionSpace Software > engineers from deployer institutions discussed this issue in February 2012 at a meeting hosted by UC Berkeley. Documentation about what was discussed is incomplete. Walker Art Center engineers who attended that meeting have also documented a proposal for how to approach the development of unified configuration that needs to be reviewed, discussed, and vetted. > Scope of Work > • Review existing documentation. > • Talk with deployer engineers about their experiences and what they need in order to improve it, make it easier, and reduce the amount of time required to configure CollectionSpace in order to bring it up for use in a stand-alone environment. > • Propose solution and vet it with community via Talk list • Develop, > test, deliver solution > Deliverables: > 1. Clear definition of problem > 2. Documented inventory of what currently exists 3. Documented set of > requirements 4. Proposed plan for development, testing and delivery 5. > Documented community conversation and feedback 6. Approved > specification for development 7. Fully developed and integrated > unified configuration solution -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

Sébastien, The first of two phases to create what we're calling a "Unified Configuration" is complete and will very likely be part of the upcoming v3.3 release later this year. Unfortunately, the current schedule for the v3.3 release is still being worked on so I don't have a specific release data for you. Within the next few days, I will update the CSPACE-5615 issue on JIRA to reflect the current state of the work. In short, the overall goal of the "Unified Configuration" is to consolidate all the CollectionSpace configuration required to extend and customize into one place. This should greatly simplify the work required to customize and extend CollectionSpace. In phase one, we unified the declaration of the data structures for CollectionSpace Objects and Procedures. The Application layer's "Record" configuration files are now the canonical place to define and change the CollectionSpace data structures. We created a command-line tool that processes the Application config files and generates all the required Nuxeo and Service layer artifacts. In phase two, this tool will also create each of the tenant service bindings files. -Richard Millet UC Berkeley, CollectionSpace Services Lead richard.millet@berkeley.edu > Sébastien Brossard <mailto:Sebastien.Brossard@smk.dk> > Wednesday, February 13, 2013 7:18 AM > Hi all, > > Looking at the JIRA, it's a bit difficult to find out what is the > current status of the Unified Configuration development. > Have we got an idea on when it could be expected? > > Thank you for your answer. > > Best regards, > Sébastien > > -----Oprindelig meddelelse----- > Fra: Richard Millet (JIRA) [mailto:collectionspace@movingimage.us] > Sendt: 17. december 2012 22:31 > Til: Sébastien Brossard > Emne: [JIRA] (CSPACE-5615) Design and Scope Discussion of Unified > Configuration > > > [ > http://issues.collectionspace.org/browse/CSPACE-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Work on CSPACE-5615 started by Richard Millet. > > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators For more information on JIRA, see: > http://www.atlassian.com/software/jira > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org