Re: Envolution proposal idea

--0-1489701126-1032104941=:80173
Content-Type: text/plain; charset=us-ascii


Just as comment, this is what we've recently done with Envolution. My team supports a several divisions of a large financial institution. Originally we used PostNuke simply to provide information via our intranet site and downloads for deployments.
Recently we've decided to use the site as a true portal. Step 1 of this was to tie the authentication system to the corporate authentication emchanism. Via LDAP a user may use their corporate ID and password to access the website and register on it. 
Of course, I've had to customize the core modules for NS-NewUser and NS-User to accomodate this but it works great. I've managed to maintain the core functions as they are, so someone like say the "admin" still uses the internal system. Registration is the same, I authenticate a user against the corporate system and pull back his/her information from the System of Record and submit that into the core registration stream. By setting a parameter I can bypass the entire hack.
The second piece of this was devising a way to handle the session out of the environment. By creating a custom API (which is mostly hacks of the original) I have a snippet of code that is placed in the header of any application we want to use the Envolution session management.

For example. Our helpdesk system is accessed by logging into the website. Once a user has logged in they get a block that displays links to the applications they have access to. In this example, the application is launched from a different server on a different domain as the main website. However, by passing the session id to this code snippet I can effectively *pass* the entire session to another application. The applciations internal user management then takes over. However the main sites iis still in effect. If you logout of the main website, your logged out of everything you have open at the time.
So, like you, I have a need for which the CMS concept sorta fits. Primarily there are pieces of it that solve exiting problems I have. My chief complaint is most everyone uses the CMS as a personal website tool to display news. Nothing else. Most everything I come up with is becuase I have it in a real world environment where the core website means very little. Sounds like your wanting to the same thing. 
-Razor
 
 Scott Kindley wrote:I have an opportunity to have Envolution installed at the Indiana
University School of Nursing.

This would not be a typical implementation of our CMS. Instead it would
be a very stripped down version that performs 1 single function.

Here is the idea and philosophy driving this idea for a proposal.

There is a need for a web interface to a medical records database. No
news posting or comments are needed. All that is required is a user
registration system just like we already have. Uopn logging in the user
would see only their home page (where you select your theme/skin, and
set preferences). Once logged in the user would be presetned with two
links ONLY..the "Change you info" link and the "Logout/Exit" link.

Clicking on the "Change your info" link would bring the user to the page
to put in their information...except the form will be much longer and
contain fields for medical records as well as basic demographic
information.

The admin user only needs a way to manage and modify user information
and post informational "news" articles.

If we can (this doesn't sound too hard) provide this we may (stress
"may") be able to get it implemented at Indiana University and may
(again stress "may") be able to use them as a test bed for the CMS and
generate white papers on it's implementation.

There is also a possibility we could also land some funding (stress
"possible" not guaranteed) for the Envolution project.

Requirements:

1) A very stripped core: Small footprint

2) Only required publishing features would be to allow the admin user to
post a simple announcement

3) Modules that would be required are the user module, lost password,
Legal module, languages, and the FAQ module.

4) Only blocks needed would be the Main Menu, and maybe a couple extra
blocks for announcements and information

This could be an excellent test bed using a major and well known medical
and nursing research institution.

There is also the opportunity for further commercial ventures by
enterprising third party developers.

This goes very well with advocacy and implementation issues with
Envolution.

I would appreciate any and all feedback on this.

Zoom



_______________________________________________
Envdev mailing list
[email protected]
http://www.madhatt.info/mailman/listinfo/envdev_madhatt.info


---------------------------------
Do you Yahoo!?
Yahoo! News - Today's headlines
--0-1489701126-1032104941=:80173
Content-Type: text/html; charset=us-ascii

<P>Just as comment, this is what we've recently done with Envolution. My team supports a several divisions of a large financial institution. Originally we used PostNuke simply to provide information via our intranet site and downloads for deployments.
<P>Recently we've decided to use the site as a true portal. Step 1 of this was to tie the authentication system to the corporate authentication emchanism. Via LDAP a user may use their corporate ID and password to access the website and register on it. 
<P>Of course, I've had to customize the core modules for NS-NewUser and NS-User to accomodate this but it works great. I've managed to maintain the core functions as they are, so someone like say the "admin" still uses the internal system. Registration is the same, I authenticate a user against the corporate system and pull back his/her information from the System of Record and submit that into the core registration stream. By setting a parameter I can bypass the entire hack.
<P>The second piece of this was devising a way to handle the session out of the environment. By creating a custom API (which is mostly hacks of the original) I have a snippet of code that is placed in the header of any application we want to use the Envolution session management.<BR><BR>For example. Our helpdesk system is accessed by logging into the website. Once a user has logged in they get a block that displays links to the applications they have access to. In this example, the application is launched from a different server on a different domain as the main website. However, by passing the session id to this code snippet I can effectively *pass* the entire session to another application. The applciations internal user management then takes over. However the main sites iis still in effect. If you logout of the main website, your logged out of everything you have open at the time.
<P>So, like you, I have a need for which the CMS concept sorta fits. Primarily there are pieces of it that solve exiting problems I have. My chief complaint is most everyone uses the CMS as a personal website tool to display news. Nothing else. Most everything I come up with is becuase I have it in a real world environment where the core website means very little. Sounds like your wanting to the same thing. 
<P>-Razor
<P>&nbsp;
<P>&nbsp;<B><I>Scott Kindley <[email protected]></I></B>wrote:
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">I have an opportunity to have Envolution installed at the Indiana<BR>University School of Nursing.<BR><BR>This would not be a typical implementation of our CMS. Instead it would<BR>be a very stripped down version that performs 1 single function.<BR><BR>Here is the idea and philosophy driving this idea for a proposal.<BR><BR>There is a need for a web interface to a medical records database. No<BR>news posting or comments are needed. All that is required is a user<BR>registration system just like we already have. Uopn logging in the user<BR>would see only their home page (where you select your theme/skin, and<BR>set preferences). Once logged in the user would be presetned with two<BR>links ONLY..the "Change you info" link and the "Logout/Exit" link.<BR><BR>Clicking on the "Change your info" link would bring the user to the page<BR>to put in their information...except the form will be much lo
 nger and<BR>contain fields for medical records as well as basic demographic<BR>information.<BR><BR>The admin user only needs a way to manage and modify user information<BR>and post informational "news" articles.<BR><BR>If we can (this doesn't sound too hard) provide this we may (stress<BR>"may") be able to get it implemented at Indiana University and may<BR>(again stress "may") be able to use them as a test bed for the CMS and<BR>generate white papers on it's implementation.<BR><BR>There is also a possibility we could also land some funding (stress<BR>"possible" not guaranteed) for the Envolution project.<BR><BR>Requirements:<BR><BR>1) A very stripped core: Small footprint<BR><BR>2) Only required publishing features would be to allow the admin user to<BR>post a simple announcement<BR><BR>3) Modules that would be required are the user module, lost password,<BR>Legal module, languages, and the FAQ module.<BR><BR>4) Only blocks needed would be the Main Menu, and maybe a couple
  extra<BR>blocks for announcements and information<BR><BR>This could be an excellent test bed using a major and well known medical<BR>and nursing research institution.<BR><BR>There is also the opportunity for further commercial ventures by<BR>enterprising third party developers.<BR><BR>This goes very well with advocacy and implementation issues with<BR>Envolution.<BR><BR>I would appreciate any and all feedback on this.<BR><BR>Zoom<BR><BR><BR><BR>_______________________________________________<BR>Envdev mailing list<BR>[email protected]<BR>http://www.madhatt.info/mailman/listinfo/envdev_madhatt.info</BLOCKQUOTE><p><br><hr size=1>Do you Yahoo!?<br>
<b><a href="http://news.yahoo.com/">Yahoo! News</a></b> - Today's headlines
--0-1489701126-1032104941=:80173--