Re: Status of mj2 development?

I'd like to second the motion for item #4.  I know there are some search
capabilities as a list administrator, but not for the users.  

To add to the wish list, some sort of pagination ( when viewing the
archives list )would be nice.  I have a list with messages back to 2002
( grouped daily ). The page gets very long and difficult to navigate.
The archives have to remain there for reference purposes. 

Dressing-up the web interface would also be nice.  I remember two years
ago when I first implemented MJ2, I left off the web interface at that
time.  I added it a year later during an upgrade.  I use it most of the
time, and I direct users to use it as much as I can.

Thanks,
 
Tim Nelson
Texas Woman's University

--- Michael Yount <[email protected]> wrote:

> Erik Pearson wrote:
> > 2. extended user information: I would need to have real names for 
> > each subscriber, and perhaps store other information.
> >   
> Real names are supported now, but storing other information would 
> probably require code changes.

I've noticed that real names are supported during subscription, but I
didn't see a way of adding a real name later when editing the
subscription list.

> > 3. subscription based on master list and site
> signup
> > key (password): The main list would be set up by
> an
> > initial dump of records from an external source,
> and
> > subsequent changes to the master user database
> would
> > all be administrative (could be hand editing a
> file.)
> > But it would be great to have "sub list"
> subscriptions
> > user-driven, with the restriction that only users
> in
> > the master list could subscribe, and also
> restricted
> > by entering a site pass key.
> >   
> To require a password for every mj_wwwusr page, you'd need to edit the

> table near the beginning of the mj_wwwusr script.

Thanks.

> > (This master list is the school registration
> database,
> > and it must be changed over every year.)
> >
> > 4. Need to be able to search the archives.
> >   
> Using what search engine?

Using mj2 of course! No, seriously, I see no reason why mj2 shouldn't be
able to search its own archives.
There may be scalability issues, but for small lists performance
shouldn't be an issue. If searchability is there, performance can always
be addressed later.

Seriously, archives without search?

> > 5. Some ui annoyances: 
> >   - changing password is too many steps,

> Sign in, visit the subscriptions page, type in the new password, and 
> press a button; how would you change that?

Actually, I mistyped -- I meant "forgot password and then change it". I
understand why the steps are necessary (basically using the email
address as a secure place to deliver sensitive information), but most
users would be used to a process involving fewer steps. Either
- answer secret question, then enter your new password or
- have email sent to your account
- click on link to reset password
- in browser, enter new password

> If the passwords are derived from an external database, why do you 
> want your subscribers to change their passwords?

In my case, passwords would not be derived from the external database,
just email address, name, and list.

> >  
> >   - navigating around and logging in/out is confusing.
> >   
> How would you improve it?

Here are some examples:

- sign in/out should be a little login box which indicates your login
status, or provides a login form if you are not logged in. It should
always be on the page at the same place.

- when browsing archives (the list view) the menu choices should be at
the top (Summary); the choice of sort order should be right there on the
list view (instead of back on the summary page)

- on many pages (e.g. the subscriptions page), there should be better
visual demarcation of the sections -- as it is they flow together, which
forces one to kind of read the entire page to find out what you want to
do. On the subscriptions page there are also multiple forms, and people
might be confused and think it is one big form and expect there to be a
"Save Changes"
button at the bottom. Perhaps it would be even better to make this into
multiple pages, so that each page is simpler. Also, end users really
don't ever need to see changeaddr, unalias, etc. With a web interface
about 1% of users (if that) will end up using the email interface (other
than unsubscribe, perhaps.)

- customizable theme -- yes, window dressing, but simply setting the
some global color settings would allow the site to more easily resemble
an existing site, especially if they get there by following a link from
a web site, and set users at ease. If stylesheets are used, this comes
for free.

Don't get me wrong, I think mj2 is great, but the web interface needs
some work to make it a pleasant experiece for general users.

Thanks!

Erik.

> 
> Michael
> 
>