History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: UP-1883
Type: Sub-task Sub-task
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Andrew Wills
Reporter: Andrew Wills
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
uPortal
Import/Export features: allows portal administrator to manage data in portal (UP-1834)

Gather Import/Export tech to a single package and version import scripts

Created: 07/Dec/07 04:43 PM   Updated: 05/Mar/08 07:59 AM
Component/s: Import / Export
Affects Version/s: None
Fix Version/s: 2.5.4, 3.0.0-M5, 2.6.2

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description  « Hide
The community seems to favor moving all import/export files (.crn, .xsl, etc) to a single package: org.jasig.portal.io.

Furthermore, import scripts (and related files) should be suffixed with an Object Model version (e.g. import-user_v2-6.crn). This approach will allow exported documents to refer to the version that imports them. When there's a change to the object model, a new script (w/ the new version) will be created and the old one will transform/add content and invoke the new script.

Export scripts do no require versioning because a single portal is only responsible for exporting to it's own native format.

 All   Comments   Work Log   Change History      Sort Order:
Andrew Wills [12/Dec/07 04:30 PM]
Done.

These enhancements will be included with the initial check in of Import/Export.