The feature list

THE FEATURE LIST

  • Datasets can be registered manually through the user interface or automatically via the API
  • Because input rules are configurable, the registration process can be as simple or as complex required

 

  • Once an input has been registered it can be shared to other domains within the system, including the public domain.
  • To prevent a mishap sharing of data and metadata is controlled by configurable policies or workflows
  • Administrators can configure user input screens to ensure that the correct metadata are captured for every type of data uploaded.
  • Whether or not information is required or optional is configurable on a field-by-field basis.
  • Users have the ability to set an embargo date which prevents publication of data until the date has past.
  • Tagging allows users to group inputs that may not have common metadata values.
  • Users can select from a list of tags when registering inputs.
  • Tags are heirarchical, meaning that when a low level tag is added to to a dataset all of the higher level tags are also automatically added.
  • Datalign allows users to register data terminals which are simply places that data are stored in the organisation. From the enterprise data warehouse to the network shared folder, all of these are data terminals.
  • Registering terminals give data managers a top down view of all of the data in an organisation
  • Some terminals can be automatically discovered and described by crawlers
  • A Processor is a mechanism that moves data from one location to another.
  • Combase builds processors but subscribers can also build and register their own
  • Pipelines combine terminals and processors to record data transformations from source through process to destination.
  • Licenses are managed at the corporate level so that domains remain consistent with each other
  • Providers are external users who can provide data via the API or through the user interface
  • Additional security is provided to protect providers from inadvertently sharing data or from accessing the datasets of other providers without authority.
  • Providers are an additional mechanism for organising data within a domain.
  • Users are able to associate data with points or areas on a map.
  • Search queries can be based on place names or by drawing a box on a map
  • Dashboards allow user to view high-level information about various activities happening within the system.
  • Supsciptions allow users to sign up to receive emails for application events relating to topics that are or interest to them.
  • Users can add filters to limit the notification conditions to meet their needs.
  • External parties can also subscribe to matters such as the status of their applications, so that they are automatically informed when things change or decisions are made
  • Users are able to manage their profile in a single place reducing the need to update multiple passwords etc.
  • Adminstrators get a top-down view of the users
  • Roles within the DMP can be tailored to meet the needs of the organisation.
  • Users are able to create and update roles by selecting descrete permissions that make up that role.
  • The role can be named and given a description for ease of administration.
  • Permissions control access to all of the features of the system.
  • Permissions are broken down to the smallest logical function, allowing the construction of tailored roles, including the ability to view only or to edit various input fields.
  • Multifactor Authentication (MFA) using a temporary security code sent via SMS when a user attempts to log into the system is enabled by default on all Datalign based systems.
  • This is one of a number of security updates implemented by Combase on the way to achieving its IRAP assessments.
  • Domains can be created by system users granted sufficient permissions.
  • A domain is both a security tool and a responsibility partition.
  • Domains can be set up to segregate data, users or areas of responsibility.
  • All Datalign systems are automatically created with a public domain. This is the only area of the system that is accessible to anonymous users.
  • The system has a public API and private API’s per domain.
  • These domains are hosted on the AWS API gateway and credentials for each domain API can be granted and revoked by domain managers.
  • APIs are managed on a domain level meaning that domain managers can grant access to their domains individually.
  • The API’s are fully documented using Swagger which means that all of the operations are documented and testable by authorised developers
  • The search system is a full featured search page including “recent searches” and pre-defined “quick searches” as well as facets.
  • Datalign offers a full text search and geospatial search using a bounding box, a boundary or a point and a faceted seach including user defined tags.
  • Security is a primary concern of the solution and one of the main reasons for the adoption of the Datalign framework.
  • By ensuring that modules are deployed automatically using audited scripts and templates, programmer errors are largely eliminated and security monitoring is automatically activated.
  • Access to repositories is limited by default and needs to be explicitly granted.
  • Security events are logged and monitored at a system level.
  • The system API is protected by the AWS API Gateway

 

  • Datalign has a powerful workflow system that allows the automation of complex business processes
  • Using the workflow module administrators can make data and metadata hidden, read only or editable at various states in the lifecycle.
  • The shareability of data and metadata is also configurable depending
  • Data uploaded into the system will be automatically retained when new datasets are uploaded, ensuring that old versions are always available if necessary
  • Datalign uses a fully featured schema repository which has its own API.
  • This means that schemas can be built and maintained in the system and be instantly collected by external tools such as Nifi or FME
  • Datalign allows for multiple layers of validation from the input of metadata through to the automated processing of data
  • Live examples include Excel spreadsheet validations that check to see that correct headings are included according to the selected schema