Login  |  Register
 
You are here February 08, 2012  
Welcome to the EMuUsers discussion forums. All registered users are encouraged to post new topics and also to participate in existing discussions.

* You must register first if you wish to make postings.
* You can subscribe to one or more forums to receive email notification when new messages are posted.
* Click on a correspondent’s name to find out their title and institution.
Subject: Support for multiple levels of access via intranet/internet
Prev Next
You are not authorized to post a reply.

Author Messages
WillScott
Posts:0

27-10-2009 10:30 AM Alert 
EMu’s built-in web controls allow only a toggle—publish to web or do not publish to web—for any record. For many museums, it may be possible to make a binary decision about web publication—share it with the public or do not share it with the public. I suspect, however, that many museums are looking to publish various levels of information for access by different kinds of users. I work quite a bit with university museums, UPMAA included. End-user categories for intranet/internet publication for a university museum include not just the public, but also students, faculty, and researchers. The museum may wish to publish a larger, but less-complete, set of data to university users than to the general public. Researchers may be given access to a different set of records, more complete than the public records, via registration and login. University and non-university museums, both, may require publication categories such as general public, researchers, and educators (K-12 and university-level), internal kiosk, etc. Furthermore, special projects may require a subset of data to be published that is geared specifically toward 3rd grade teachers, for example.

EMu does not seem to include this sort of intranet/internet-access control in default configurations. (I know of at least two museums that are paying for more detailed controls designed in-house as customizations). Things could certainly get out of hand trying to accommodate each institutions specific needs in this area. But I think that there may be a middle ground.

In its simplest implementation, this may include 1-n levels of intranet/internet publication that could be defined by the client via a dropdown. In that scenario, users could set objects to be published to the public (www), researchers (www with approved registration), intranet (university), intranet (museum), etc. Any number of categories could be set by adding terms to the dropdown field controlling the levels of access. Clients would be largely responsible for handling which records are presenting to end users based on that field. KE may also include the field as part of its PHP Web Toolkit so clients would not have to throw broad IFs in front of the KE code.

A more complicated option would be an altered copy of the EMu Security controls that limit in-house access to records, tabs, and fields. That would allow an even greater level of control. Publication of records would be based on end-user “groups” or categories.

I am interested to hear from other users how they are publishing different information to different sites and how they think EMu’s default publication options might better accommodate their needs. I would be glad to collaborate on a proposed specification for improving publication options, as well, if other clients are interested.

Thanks and best wishes,

Will

Will Scott
Museum and Computer Consultant (presently working with UPMAA)
Brooklyn, NY

William Real
Posts:47

19-11-2009 3:58 AM Alert 
Hi Will,

I meant to chime in on this earlier. We probably do not require as many levels as the university you describe, but we definitely have at least 3 levels of access that we want to implement, at least for multimedia. We would like to hear from other users--if this functionality became part of the standard client, would it be a benefit to you?

Will
You are not authorized to post a reply.
Forums > EMu Development > Web Development > Support for multiple levels of access via intranet/internet



ActiveForums 3.6