This week, you might choose to comment on how suitable Drupal might be for your collection. Begin to develop some criteria you would use to judge how well an application such as Drupal meets the needs of your collection and its users. We will expand on this problem over the semester.
It seems that the advantage of Drupal is, in short, management. In order to benefit from the management features, there need to be contributors. Hopefully, if building a digital library of items, people would not be assigned such a project alone, so I see Drupal being very beneficial for any project involving several contributors and regular updates.
My collection is a small sample, so it is difficult to see the benefit in the case of fifteen items which will remain static so long as I am the only one working on it. Features in content management, user management, and site building do show a great deal of flexibility. I can regulate which authenticated users control precisely which actions (e.g. creation, editing, deletion) in precisely which areas of expertise (e.g. planes, trains, automobiles, you name it, etc). Modules create even more options to explore, but from those that I used (date & cck), they were options which I could already control from site building. Well, the modules do speak for an active community of developers and certainly contain useful tools (if you can find them).
No comments:
Post a Comment