This project is not covered by Drupal’s security advisory policy.
The Research Annotator module provides you with the ability to annotate html elements
of node body content through the field_body field.
Installation
Follow the standard contributed module installation process:
http://drupal.org/documentation/install/modules-themes/modules-7
Requirements
Dependencies include the following modules.
- Block
- ctools
- entity
How it Works
Once configured, this "block" allows people to annotate node content. Each annotation is associated with a node revision rather than the node itself so if you want to revert node revisions, annotations are preserved. Once a new node revision is created, new annotations
can be associated with the new revision.
Configuration
- Go to any content type and modify its body field (for example, go to example.com/admin/structure/types/manage/page/fields/body). Configure the Research Annotator settings. NOTE, it is also recommended you set the default output filter of the body field to "Annotation Safe Output".
- Configure CRUD permissions regarding research annotations.
IMPORTANT Recommendations
- Use the "Annotation Safe Output" filter on body content that is being annotated.
- Use a LARGE block region for displaying annotations. This block region should also be to the left or right of the content being annotated.
- When modifying tpl files in your theme, do not remove or modify existing element attributes. Adding new attributes is safe. The reason for this is the heavy use of jQuery for this module to function correctly.
Limitations
- This module is currently only operating on the field_body field and no other textarea field.
- You can only annotate the FIRST value of a body field.
- Currently, there is no multilingual support for annotation text.
Project information
Minimally maintained
Maintainers monitor issues, but fast responses are not guaranteed.Maintenance fixes only
Considered feature-complete by its maintainers.- Project categories: Content editing experience, Content display
- Created by captainpants on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
