[Exist-development] New eXist admin webapp - features list

[Thomas W. <tho...@gm...>]

Dear all,

There are always more then one way to do one job - with XForms or with XSLT
it is a question of personal preferences. We can have more them one
implementation and people will gravitate to what they prefer.

I do not think it s the technology that defines the value of an application.
It is how well it does the main functions, how easy it is to  maintain and
extend and and new features etc.

Let us try to define what could be the best possible set of features and
then start implementing them following the principle of 20:80 - start from
these 20% features that are used 80% of the time.

I think we can have the following main areas:
*  A.  Server Configuration:*
        1) have all config files available to change/set via web
interface: activate/deactivate modules; memory settings etc.
        2) Clone eXist configuration with save/restore of all settings,
transferable to other server.
        3) Set directories: data, backup, fs
        4) Indexes, triggers
        5) URL rewriting

* B. Server information (view only):*
        1) Status,
        2) statistics
        3) performance monitor.
        4) profiling

* C. Job management*
      1) Currently running jobs
      2) Scheduled jobs
      3) Kill jobs, change job priority

* D. Admin actions:*
       1) Shutdown, restart
       2) Backup/Restore
       3) Run build and restart
       4) Reindex

*E. Security, User and Group Management*
      1) default security settings for collection and user
      2)  Users: single and bulk operations
      3) Groups
      4) Bulk(recursive) security operations

*F. Data: Collections and Resources*
     1) browse collections/resources:
          1.a. GIU with windows explorer style interface - folder tree on
the left, content on the right.
          1.b. Fast content browser where we see only the content of the
current entity and a cookie bread crumble at the top, for back and up
navigation. Clicking on a collection name or a resource will display its
contents. Every collection will have in brackets after its name {number or
sub collections}/{number of resources}. A resource will have its size after
its name. We can have views that present the content in a content specific
way like thumbnails if the collection contains images.
          1.c. Special attention should be paid to dealing with large number
of entities. We can have some way to summarize the content. We need
pagination, sorting and filtering.
     2) Security Operations on collections and resources: permissions,
groups, ownership
           2.a. single selected object
           2.b. multiple operation on selection by: checkbox, name, date,
mime type or other filtering criteria.
           2.c. recursive operations
     3) content operation
          3.a. Import: file, directory, directory with sub-folders
          3.b. Export: file, collection, collection with sub-collections


Have I missed something?

Thomas


------

Thomas White

Mobile:+44 7711 922 966
Skype: thomaswhite
gTalk: thomas.0007
Linked-In:http://www.linkedin.com/in/thomaswhite0007
facebook: http://www.facebook.com/thomas.0007