Just for the record, at the other end of the spectrum from
'lightweight project' you might consider speaking to Peter Stokes at
KCL about what it would take to build an adjunct to the Digital
Resource for Palaeography project <http://www.digipal.eu/>, which
includes a feature for annotating in manuscript images and recording
in a database example of letterforms. Examples of abbreviations and
other interesting forms from Greek papyri could presumably in a
similar way be mapped to images from APIS, Papyri.info, etc.
There isn't currently a papyrological use-case for DigiPal, but as
Peter knows, I would love to work with someone who has one. (It would
take funding though.)
For what it's worth,
G
On 25 April 2012 09:35, John Birchall <[log in to unmask]> wrote:
> Dear Gregg,
>
> As someone who has some training in both Greek and Demotic Egyptian
> papyrology, and is now making a living from CMS websites in Drupal and
> Wordpress (and offering daily 'spirit of open source', i.e. unpaid, Drupal
> support http://drupal.org/user/710760), my first thought is that maybe it
> makes sense to list design requirements in more detail before choosing an
> architecture.
>
> You do not say, but I assume, that your interest is in Greek papyrology.
>
> Drupal offers, out of the box,
> tagging ('taxonomy' in Drupal language) with multiple and hierarchical
> vocabularies, custom fields (fields which can be attached to a piece of
> content, a user, or a custom entity in the database). Drupal permits the
> creation of custom entities (to be used if each entry is a custom entity
> rather than a piece of content or node: but little software has been written
> yet for custom entities, most contributed software is for content 'nodes'),
> and a contributed entity api. It has Views module (permitting selection,
> sorting and display of nodes or entities or users by any possible selection
> of field).
> Drupal also offer multiple custom editorial roles, and (with Workbench
> modules) content moderation by customised rights per role, and visualisation
> of revision information.
>
> I guess building the site in English makes most sense, but Drupal does has
> comprehensive and robust multi-language support including right-to-left,
> though the complexities of implementing multi-language are greater than
> first meet the eye.
>
> I do not recommend Drupal for very lightweight projects as it does involve
> more maintenance and better hosting than Wordpress.
>
> John Birchall
>
>
>
> -----Original Message-----
> From: The Digital Classicist List [mailto:[log in to unmask]]
> On Behalf Of Schwendner, Gregg
> Sent: 25 April 2012 02:45
> To: [log in to unmask]
> Subject: [DIGITALCLASSICIST] collaborative website for sigla and
> abbreviations
>
> I am going to start a website to illustrate papyrological sigla and
> abbreviations. Any suggestions as to what type of site would accomplish this
> best? A blog (not sure tagging would be a sufficient organizing principle)?
> A wiki? PDF files?
> The idea would be that editors could, should they wish, add examples on
> their own. The editor(s) could standardize the entires as time permits.
>
> Thanks for your consideration,
> Gregg Schwendner
--
Dr Gabriel BODARD
(Research Associate in Digital Epigraphy)
Centre for Computing in the Humanities
King's College London
26-29 Drury Lane
London WC2B 5RL
Email: [log in to unmask]
Tel: +44 (0)20 7848 1388
Fax: +44 (0)20 7848 2980
http://www.digitalclassicist.org/
http://www.currentepigraphy.org/
|