[sword-devel] SWORD utils frontends
bergmannmd at web.de
Mon May 18 09:19:41 MST 2009
Actually I'd like to further work on the web application.
In the last two years I've done quite a bit on Java web applications
and started to like it.
Maybe we can further talk about it and define requirements in 2 1/2
weeks when I'm back from vacation.
Am 17.05.2009 um 19:24 schrieb Troy A. Griffitts:
> Dear Manfred,
> If you decide to continue down the web route, as DM mentioned, we
> plan to have a web tool to let organizations and other users manage
> their own library of SWORD modules (we've had requests for this from
> some of the larger orgs that use our stuff). There is the start of a
> libmaint/ module on our community site, which lets a user add a module
> to their own private ~community/webapp/users/<username>/library/ SWORD
> library. It doesn't do much right now except create the mods.d/ and
> modules/ if they don't exist and then they can add a 'Document' which
> created a mods.d/<docname>.conf file and modules/<docname>/, but
> actually create any data files.
> Have a look at the JSP code if you want. It's a very rough proof of
> concept, but might be useful if you continue down this route.
> Manfred Bergmann wrote:
>> I started working on web frontends for the SWORD utilities
>> (osis2mod, xml2bgs, ...) and also for OSIS validation.
>> It can happen that many people use this at the same time and to not
>> mix up modules and uploaded OSIS or source files the application
>> needs either:
>> - create temporary session folders on the server where data is
>> temporarily stored and processed for the current session only and
>> deleted some time later.
>> - work on a user name related bases. That would mean have a login
>> before someone could actually use the frontends. User folders could
>> be created to operate in and the user could get an interface for
>> managing his modules (at a later stage).
>> In my opinion the user approach has more potential. But in order to
>> not again have users need to register while they may already have
>> an account for our wiki it might be good to have some kind of
>> single-signon. Or at least share user data in a database which can
>> be used for the wiki and this service.
>> Since the wiki database already exists would it be possible to
>> access this database and share the users in there?
>> sword-devel mailing list: sword-devel at crosswire.org
>> Instructions to unsubscribe/change your settings at above page
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel