Drew, This proposal sounds great to me, we at Hopkins are particularly excited about the features you outlined. I'd also like to note that the design should allow for web services to be built around the implementation so we are not entirely reliant on command line administrative ant tasks for execution, and so we can build independent administrative UIs around the functionality.
Looks great! --Chris > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:bounce-5167801- > [EMAIL PROTECTED] On Behalf Of Drew Wills > Sent: Wednesday, October 31, 2007 5:50 PM > To: [email protected] > Subject: [uportal-dev] PROPOSAL: Import/Export for 3.0, 2.6.2, 2.5.4 > > Dear community, > > After consulting some knowledgeable community members and colleagues, I > believe the time is right for including the Cernunnos-based > Import/Export features with the uPortal project itself. > > I have updated JIRA UP-1834 > (http://www.ja-sig.org/issues/browse/UP-1834) to reflect this proposal > in detail. > > Here is a brief summary of the proposed changes: > - Most of the out-of-the-box data set gets removed from data.xml. > - These items get represented as individual XML documents; the data > itself is unchanged > - These documents get imported (through the tool) in the 'db' target > - Lower-level 'import' and 'export' targets (exactly as found in > import-export.xml) get added to build.xml > > Highlights/advantages of these changes include: > - They make uPortal data significantly more accessible to humans > outside the UI > - They make it easy to migrate entities from one environment to > another, such as: > - 2.5/2.6 to 3.0 > - 'QA' to 'prod' > - 'portal.yale.edu' to 'my.wisc.edu' > - They offer a solid foundation on which other entity-manipulation > tools may be built > > Here's where we propose to make these changes: > - trunk/ (3.0) > - rel-2-6-patches (after 2.6.1 is cut) > - rel-2-5-patches (Capabilities only -- no changes to build or > data.xml) > > Some additional points: > - To start with, all data (users, groups, channels, memberships, > permissions, layouts) remains the same as it ever was; of course -- > the > community is free to evolve this data subsequently > - Setup & Deployment of the portal is unchanged; 'deploy', 'db', > and > 'initportal' work just as always > > Please respond with your thoughts. I would like form a consensus on > this proposal so I can pull the trigger as time permits. > > cheers all, > > drew wills > > -- > Andrew Wills > UNICON, Inc. > Office: (480) 558-2476 > http://code.google.com/p/cernunnos/ > > -- > You are currently subscribed to [email protected] as: > [EMAIL PROTECTED] > To unsubscribe, change settings or access archives, see http://www.ja- > sig.org/wiki/display/JSG/uportal-dev -- You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
