Re: [uportal-dev] PROPOSAL: Import/Export for 3.0, 2.6.2, 2.5.4

[Eric Dalquist]

It sounds like a great feature and plan,

+1

-Eric

Drew Wills wrote:

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 documents get imported (through the tool) in the 'db' target


Highlights/advantages of these changes include:

    - 2.5/2.6 to 3.0
    - 'QA' to 'prod'
    - 'portal.yale.edu' to 'my.wisc.edu'


Here's where we propose to make these changes:
  - trunk/ (3.0)
  - rel-2-6-patches (after 2.6.1 is cut)


Some additional points:




cheers all,

drew wills

- These items get represented as individual XML documents; the data itself is unchanged - Lower-level 'import' and 'export' targets (exactly as found in import-export.xml) get added to build.xml - 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: - They offer a solid foundation on which other entity-manipulation tools may be built - rel-2-5-patches (Capabilities only -- no changes to build or data.xml) - 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.

smime.p7s
Description: S/MIME Cryptographic Signature