Very nice summary. At this point we still need to work out if the RFE in UP-1842 represents some functionality that wasn't already added by the work on UP-1413 or not so we can see when it should be scheduled for inclusion.
-Eric Drew Wills wrote: > Andy & Eric, > > The Import/Export features I've been using -- described on the uPortal > wiki > (http://www.ja-sig.org/wiki/display/UPC/uP2+XML+Import+Export+with+Cernunnos) > and covered by a new JIRA > (http://www.ja-sig.org/issues/browse/UP-1834) -- would also cover this > need. > > They use the tried-and-true pubchan file format to import channels, > but they don't rely on ordering or specifying database IDs. > > These tools also allow you to manage the following other entity types > in XML documents, also without database IDs: > - Groups > - Memberships > - Users > - Layouts > - Permissions > > Instead of using database IDs, these tools link up new entities with > their dependencies as they are imported. For example, entities will > be processed in the following order on an 'initportal': > - Template Users > - Users > - Groups > - Channels > - Memberships > - Permissions > - Layouts > > Thereafter, any entity may be imported (in any order) so long as the > things it relies on are already present. > > These tools also export to the same format they support on import. > Just type > > > ant -f import-export.xml export -Ddir=mystuff -Dtype=all > > To export your whole portal universe to a directory called stuff/. > > These tools can be retrofitted (w/o modifying existing files) to > earlier versions of uPortal (2.5 & up). Put them into your 2.5.3 > portal, export all your users, layouts, channels, groups, and > permissions, then import them into a 2.6. > > These tools are already in use at CSU Chico & University of Colorado > System. > > Some notable list members -- e.g. Chris Doyle of JHU & Faisan from > Rutgers -- have given them a spin as well. Chris provided valuable > feedback over a period of weeks, and (in particular) identified a > serious issue using these tools and MS SQL Server. Andrew Petro, Adam > Rybicki, and myself worked out a plan to resolve the issue, but it > hasn't been implemented or integrated with the existing technology. > > drew wills > > > Eric Dalquist wrote: >> Andy, >> >> A quick peak at the 2.6.1 RC2 code shows a <channelId> element in >> each of the chanpub files in use. The data.xml for 2.6.1 has no >> UP_CHANNELS table declared and the channel IDs come from that >> <channelId> element. Is this what you need? It looks like this change >> happened for http://www.ja-sig.org/issues/browse/UP-1413 which made >> it into 2.6.0 >> >> -Eric >> >> Andy Gherna wrote: >>> >>> Hello all, >>> >>> >>> >>> An issue was recently submitted to JIRA >>> (http://www.ja-sig.org/issues/browse/UP-1842). To summarize the >>> issue, in the past we have experienced some varied behavior when >>> publishing channels, particularly when the portal was initialized. >>> Channels would appear in unexpected places and we would have to very >>> carefully edit the data.xml file to get everything right. Sometimes >>> it would work right on a Windows workstation but not a Mac or Unix >>> and vice versa. >>> >>> >>> >>> We have submitted an enhancement that overcomes this behavior. In >>> particular, we have presented 2 options. The first was to sort the >>> channel files in a consistent way when deploying to make sure that >>> channel ids would match up with what we had in our data.xml. The >>> second was to modify the channelDefinition.dtd with a new (optional) >>> tag: CHANID. This would register a channel with the database with >>> the given ID (e.g. <CHANID>262</CHANID> could be included in the >>> channel publishing xml). >>> >>> >>> >>> We have been using the first option for about a year and a half now >>> and the second since January. Both have been working fine for us. >>> >>> >>> We have posted diffs of all the source files that were changed with >>> the issue. I was hoping that even though we are at feature >>> completeness for 2.6.1 that this could be rolled in to 2.6.1. >>> Thanks for your consideration. >>> >>> >>> >>> -- >>> >>> Andy Gherna >>> >>> CITES, University of Illinois >>> >>> Senior Research Programmer >>> >>> Email: [EMAIL PROTECTED] >>> >>> Phone: (217) 265-9490 >>> >>> >>> >>> >>> -- >>> 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 >
smime.p7s
Description: S/MIME Cryptographic Signature
