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

Key: UP-1898
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Andrew Wills
Reporter: Eric Dalquist
Votes: 2
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
uPortal

Document the use of the Import/Export tools in the uPortal Manual

Created: 10/Jan/08 04:05 PM   Updated: 19/May/09 09:37 PM
Component/s: Import / Export
Affects Version/s: None
Fix Version/s: None

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


 Description  « Hide
There needs to be clear and accurate information on:
  - How to use Import/Export
  - How it ,works (high-level view)

 All   Comments   Work Log   Change History      Sort Order:
Arlo White [07/Jan/09 05:14 PM]
I'll writeup some documentation when CalPoly is done with our 3.1 rollout.

Arlo White [11/Feb/09 07:09 PM]
I've documented a lot of this here:
http://www.ja-sig.org/wiki/display/UPM30/01+Database+Migration

Feel free to move the pages if you believe they belong somewhere else.


Dustin Schultz [13/Mar/09 09:06 AM]
I'd like to see a section title "What's Missing" or "Known Issues" so that others are aware of any problems before they embark upon the migration.

Christopher J. Holdorph [05/May/09 04:13 PM]
Adjusting priority. The Jira definition for 'Critical' is "Crashes, loss of data, memory leak". This issue does not cause any of those things to occur. At most it could be considered "Major" with existing priority options available. If this is insufficient for the original reporter, then maybe we should create some additional priority options, to distinguish documentations that are more important that 'major', but are not the same as code that causes a project to crash.