Advanced Usage

The account adapter

The app provides an adapter that you can use to customize behavior for Accounts. You can override this setting by specifying the ANVIL_ACCOUNT_ADAPTER setting in your settings.py file. By default, the app uses DefaultAccountAdapter, e.g.,:

ANVIL_ACCOUNT_ADAPTER = "anvil_consortium_manager.adapters.default.DefaultAccountAdapter"

To customize app behavior for accounts, you must subclass BaseAccountAdapter and set the following attributes:

The following attributes have defaults, but can be overridden:

  • account_link_email_subject: Subject line for AnVIL account verification emails. (Default: "Verify your AnVIL account email")

  • account_link_email_template: The path to account verification email template. (Default: anvil_consortium_manager/account_verification_email.html)

  • account_link_verify_message: Message to display after a user has successfully linked their AnVIL account. (Default: "Thank you for linking your AnVIL account.")

  • account_link_redirect: The URL to redirect to after a user has successfully linked their AnVIL account. (Default: settings.LOGIN_REDIRECT_URL)

  • account_verification_notification_email: Email address to send an email to after a user verifies an account. If None, no email will be sent. (Default: None)

  • account_verification_notification_template: The path to the template for the account verification notification email. (Default: anvil_consortium_manager/account_verification_notification_email.html)

Optionally, you can override the following methods:

  • get_autocomplete_queryset(self, queryset, q): a method that allows the user to provide custom filtering for the autocomplete view. By default, this filters to Accounts whose email contains the case-insensitive search string in q.

  • get_autocomplete_label(self, account): a method that allows the user to set the label for an account shown in forms using the autocomplete widget.

  • after_account_verification(self, account): a method to perform any custom actions after an account is successfully linked. If an exception is raised by this method, account linking will still continue and site admins will be notified via email.

  • get_account_verification_notification_context(self, account): a method to provide custom context data for the account verification notification email. This method is passed the account object and should return a dictionary of context data.

  • send_account_verification_notification_email(self, account): a method to send an email to the address specified in account_verification_notification_email. By default, this method calls the get_account_verification_notification_context method to get the context data for the email and sends an email to the address specified by account_verification_notification_email (if set). If an exception is raised by this method, account linking will still continue and site admins will be notified via email.

The Managed Group adapter

The app provides an adapter that you can use to customize behavior for Managed Groups. You can override this setting by specifying the ANVIL_MANAGED_GROUP_ADAPTER setting in your settings.py file. By default, the app uses DefaultManagedGroupAdapter, e.g.,:

ANVIL_MANAGED_GROUP_ADAPTER = "anvil_consortium_manager.adapters.default.DefaultManagedGroupAdapter"

To customize app behavior for accounts, you must subclass BaseManagedGroupAdapter and set the following attributes:

Optionally, you can override the following methods:

  • after_anvil_create(self, managed_group): a method to perform any actions after creating the Managed Group on AnVIL via the ManagedGroupCreate view.

The workspace adapter

The app provides an adapter that you can use to provide extra, customized data about a workspace. Unlike the other adapter classes above, you can specify any number of custom adapters in your settings file.

The default workspace adapter provided by the app is DefaultWorkspaceAdapter. The default workspace_data_model specified in this adapter has no fields other than those provided by BaseWorkspaceData. This section describes how to store additional information about a workspace by setting up a custom adapter.

First, you will need to define a new model with the additional fields. It must inherit from BaseWorkspaceData, which provides a one-to-one field called workspace to the Workspace model.

from django.db import models
from anvil_consortium_manager.models import BaseWorkspaceData

class CustomWorkspaceData(BaseWorkspaceData):
    study_name = models.CharField(max_length=255)
    consent_code = models.CharField(max_length=16)

You must also define a form containing the additional fields. You must include the workspace field, which will automatically be linked to the new Workspace when creating or importing a workspace.

from django.forms import ModelForm
from models import CustomWorkspaceData

class CustomWorkspaceDataForm(ModelForm):
    class Meta:
        model = CustomWorkspaceData
        fields = ("study_name", "consent_code", workspace")

Optionally, you can define a new django-tables2 table to use in place of the default WorkspaceStaffTable that comes with the app. This is helpful if you would like to display fields from your custom workspace data model in the Workspace list view. This table will need to operate on the Workspace model, but it can include fields from your custom workspace data model. If you do not want to define a custom table, you can use the default table provided by the app: anvil_consortium_manager.tables.WorkspaceStaffTable.

import django_tables2 as tables
from anvil_consortium_manager import models as acm_models

class CustomWorkspaceDataTable(tables.Table):
    name = tables.columns.Column(linkify=True)
    class Meta:
        model = acm_models.Workspace
        fields = ("customworkspacedata__study_name", "workspacedata__consent_code", "name")

Next, set up the adapter by subclassing BaseWorkspaceAdapter. You will need to set:

  • name: a human-readable name for workspaces created with this adapater (e.g., "Custom workspace"). This will be used when displaying information about workspaces created with this adapter.

  • type: a string indicating the workspace type (e.g., "custom"). This will be stored in the workspace_type field of the anvil_consortium_manager.models.Workspace model for any workspaces created using the adapter.

  • description: a string giving a brief description of the workspace data model. This will be displayed in the WorkspaceLandingPage view.

  • workspace_form_class: the form to use to create an instance of the Workspace model. The default adapter uses WorkspaceForm`.

  • workspace_data_model: the model used to store additional data about a workspace, subclassed from BaseWorkspaceData

  • workspace_data_form_class: the form to use to create an instance of the workspace_data_model

  • list_table_class_staff_view: the table to use to display the list of workspaces for Staff viewers

  • list_table_class_view: the table to use to display the list of workspaces for non-Staff Viewers.

  • workspace_detail_template_name: the template to use to render the detail of the workspace

The following attribute for WorkspaceListByType view has a default, but can be overridden: * workspace_list_template_name: a path to the template to use to render the list of the workspace

You may also override default settings and methods:

  • get_autocomplete_queryset: a method to filter a workspace queryset for use in the WorkspaceAutocompleteByType view. This queryset passed to this method is the workspace data model specified by the adapter, not the Workspace model.

  • get_extra_detail_context_data: a method to add extra context data to the WorkspaceDetail view. This method is passed the Workspace model, not the workspace data model specified by the adapter.

  • before_anvil_create: a method to perform any actions before creating a workspace on AnVIL via the WorkspaceCreate view.

  • after_anvil_create: a method to perform any actions after creating a workspace on AnVIL via the WorkspaceCreate view.

  • after_anvil_import: a method to perform any actions after importing a workspace from AnVIL via the WorkspaceImport view.

Here is example of the custom adapter for my_app with the model, form and table defined above.

from anvil_consortium_manager.adapters.workspace import BaseWorkspaceAdapter
from anvil_consortium_manager.forms import WorkspaceForm
from my_app.models import CustomWorkspaceData
from my_app.forms import CustomWorkspaceDataForm
from my_app.tables import CustomWorkspaceStaffTable

class CustomWorkspaceAdapter(BaseWorkspaceAdapter):
    name = "Custom workspace"
    type = "custom"
    description = "Example custom workspace type for demo app"
    list_table_class_staff_view = tables.CustomWorkspaceDataStaffTable
    list_table_class_view = tables.CustomWorkspaceDataUserTable
    workspace_form_class = WorkspaceForm
    workspace_data_model = models.CustomWorkspaceData
    workspace_data_form_class = forms.CustomWorkspaceDataForm
    workspace_detail_template_name = "my_app/custom_workspace_detail.html"
    workspace_list_template_name = "my_app/custom_workspace_list.html"

Finally, to tell the app to use this adapter, set ANVIL_WORKSPACE_ADAPTERS in your settings file, e.g.: ANVIL_WORKSPACE_ADAPTERS = ["my_app.adapters.CustomWorkspaceAdapter"].

To define multiple adapters for different types of workspaces, e.g.:

ANVIL_WORKSPACE_ADAPTERS = [
    "my_app.adapters.FirstWorkspaceAdapter",
    "my_app.adapters.SecondWorkspaceAdapter",
]

as long as you have defined both FirstWorkspaceAdapter and SecondWorkspaceAdapter in your code. If you define multiple workspaces, the index page and the navbar that comes with the app will show links for each different type of workspace.

If you would like to display information from the custom workspace data model in the WorkspaceDetail view, you can include it in the workspace_data block of the workspace_detail.html template. For example:

{% extends "anvil_consortium_manager/workspace_detail.html" %}
{% block workspace_data %}
<ul>
  <li>Study name: {{ workspace_data_object.study_name }}</li>
  <li>Consent: {{ workspace_data_object.consent_code }}</li>
</ul>
{% endblock workspace_data %}

If custom content is not provided for the workspace_data block, a default set of information will be displayed: the billing project, the date added, and the date modified.

Customizing the Workspace form

Most workspace adapters can set workspace_data_form to WorkspaceForm. This will use the default form provided by the app.

If you would like to add a custom form (e.g., to provide custom help text or do additional cleaning on fields), you can set workspace_data_form to a custom form. You must subclass anvil_consortium_manager.forms.WorkspaceForm. If you modify the form Meta class, make sure that it also subclasses WorkspaceForm.Meta:

from anvil_consortium_manager.forms import WorkspaceForm

class CustomWorkspaceForm(WorkspaceForm):

    class Meta(WorkspaceForm.Meta):
        help_texts = {"note": "Custom help for note field."}