Drupal Developer for 'Virtual Document Management Module'

As part of a website project, which is a legal information portal, and forum for the concerns of small scale food producers, there is a functionality which we are calling a 'Document Manager'. This is a virtual folder system, for paid subscribers of the website, which allows the virtual storing of and actions(print/download) of 'legal documents' found within the sites extensive database of information, primarily legal documentation, being 'bookmarked' for easy future access.

We have Admin who will be adding these documents to a database.

We are using the CMS system Drupal, and work done includes HTML of key pages, with grid, CSS, and CMS mostly built. Designs are signed off with our client and need to be adhered to as closely as is possible.

Separately to the below, a search engine will be built to make documents findable for the below functionality.

The elements below are needed, to be implementable Drupal modules.
Tech list first - more detailed functionality spec below.

________


NOTES FROM DEVELOPER:
1) Document management module

Admin can:

- Create documents - various layouts... not important at this stage. structured text (h1, h2, p, formatting etc). html output would be ideal. xsl?
- Content of documents needs to be searchable by Users, documents need tags (admin builds a taxonomy)

Subscribed users:

- Member area [see visual: dropbox/AFL/4-subscriber-area.psd]
- ray to provide html

This is a virtual folder system. Documents can be organised into folders (groups), users can read, email, download documents (as pdf).

Users can annotate documents.
This is an important feature. Not super complicated, but users must be able to leave notes related to documents (1:N).
This does not have to be super complex: I think this approach (simple, functional, fast) might suit. Open to ideas.

1) anchoring.
user clicks a side bar at line they want to leave an annotation
post note (ajax is ok, but must have fallback)
note can live (visually) in a notes area, but it can be href'd anchored to that particular part of the document?
some complexity may arise if we have document (visually) as N pages. anchor > document[page][line]

Ideally access to each feature provided under the member area could be controlled.

e.g.

User Group Registered
- read
- create folder
- folder actions

User Group Registered Subscribed
- read
- annotate
- email
- download
- create folder
- folder actions

Some guidelines, nothing heavy:
• we do not need css. however we need the html output properly id'ed and classed where appropriate, be logical:
• e.g.
• document folder view, an open folder might look like
• foo
• and closed
• foo User clicks 'View Document', Document is displayed from database in 'legal house style'


____________________________
Anyone quoting should be prepared to sign a privacy agreement for content of the site. Usual standard signature form. Thanks.