To create or edit a new specialist document you will have to make changes to this application, publishing-api and search-api. You will not have to make any changes to frontend applications.
See example PR here
-
Add any new field definitions to this file
-
Add examples as instructed. You can copy and paste from another specialist document format, only changing what is necessary (you can leave the body and headers unchanged).
You'll need to generate your own UUIDs for the
content_id
andsignup_content_id
fields:$ irb irb(main):001:0> require "securerandom" => true irb(main):002:0> SecureRandom.uuid => "5087e8b6-ee54-40f9-b592-8c2813c7037d"
-
Run
bundle exec rake build_schemas
to regenerate schemas.
When the PR is reviewed and its tests passing, it can be merged and deployed at this point.
See CMA cases.
New formats should be added with target_stack: "draft"
so that departments can preview the finder before you publish it.
See CMA cases
See CMA cases
Search API needs copies of the schema very similar to the one in Specialist Publisher. See:
- CMA case schema (example)
- field definitions
You'll also need to add your document format to:
- the main ES types list govuk.json
- migrated_formats.yaml
- mapped_document_types.yaml
Finally, you'll need to add your custom fields to:
The email sign up page is rendered by Finder Frontend using the configuration in the new schema added to specialist publisher. The schema should specify email_filter_by
and email_filter_facets
(e.g. cma-cases).
If your email sign up page should have checkboxes (e.g. cma-cases), you will need to edit email-alert-api by adding the new tags to valid_tags.rb.
To deploy a new finder for previewing:
- Ensure the finder target_stack is set to
draft
- Merge and deploy Publishing API and Specialist Publisher.
- Ensure you deploy Publishing API first, to avoid schema validation errors.
- Also deploy Email Alert API if you have made changes to it.
- Publish the finder to the draft stack by running the rake task
publishing_api:publish_finders
orpublishing_api:publish_finder[your_format_name_based_on_the_schema_file]
against the specialist publisher app (rake tasks here). - Wait for department's feedback and approval and agree on a release date
To release the finder to the live stack:
- Prepare before the agreed release date. Merge PRs and release on agreed date.
- Merge and deploy Search API
- Reindex the govuk Elasticsearch index.
- This takes around 30-45 minutes on Production, or 3-4 hours on Integration.
- Alternatively, run
search:update_schema
for a shorter run. Make sure the this is run before any documents are published, otherwise a full reindex will be required. - NB: reindexing shouldn't really be necessary; Elasticsearch will dynamically create the field mappings the first time a new document of this type is published. In other words, if you publish a new document type, the finder will work and it will return the relevant documents even without a reindex. However, the filters on the finder would not work, as this reindexing job also builds the filters for the finder, so we have to run the job.
- Change the target_stack of the finder from
draft
tolive
in specialist-publisher json schema config - Merge and deploy Specialist Publisher
- Publish the finder by running the rake task
publishing_api:publish_finders
orpublishing_api:publish_finder[your_format_name_based_on_the_schema_file]
against the specialist publisher app (rake tasks here).
Specialist Publisher grants access to the publishing interface for your new document type to the following Signon users:
- Users that belong to the owner organisation AND have
Editor
permissions - Users that have the permission
your_new_document_type_editor
, e.g.oim_project_editor
You'll need to create the new permission manually.
We often receive requests to add new fields to a specialist document or to add new values to existing fields.
-
In
publishing-api
:- Add the new field in the specialist_document schema, and add the new values. See example commit.
- Update the facets in the corresponding example json with the additional values.
NOTE: You will need to run
bundle exec rake build_schemas
to regenerate schemas after adding the new value(s). -
In
specialist publisher
:
See this commit for an example.
- In
search-api
, add the new field in the following places (see this commit for an example):- the relevant schema in the elasticsearch_types directory.
- the elasticsearch_presenter.
- the specialist_presenter.
- the field_definitions file.
To republish the finder:
- Deploy Publishing API, Search API.
- Run
search:update_schema
on Search API. If this errors, you may have to do a full reindex. - Deploy Specialist Publisher, deploy after the Search API schema update / reindex to avoid users publishing new documents with the new field.
- Publish the finder by running the rake task
publishing_api:publish_finders
orpublishing_api:publish_finder[your_format_name_based_on_the_schema_file]
against the specialist publisher app (rake tasks here).
-
In
publishing-api
:- Add the new values to the field you are amending, in the specialist_document schema. See example here.
- Update the facets in example json with the additional values, as in this commit.
NOTE: You will need to run
bundle exec rake build_schemas
to regenerate schemas after adding the new value(s). -
In
specialist publisher
, add the new values to the relevant file in the schema directory. See this commit for an example. -
In
search-api
, amend the value in the relevant schema in the elasticsearch_types directory. See this commit for an example.
To republish the finder:
- Deploy Publishing API, Search API, Deploy Specialist Publisher.
- Publish the finder by running the rake task
publishing_api:publish_finders
orpublishing_api:publish_finder[your_format_name_based_on_the_schema_file]
against the specialist publisher app (rake tasks here).
The schema files that define a specialist document, are also used to configure that document's specialist finder. See this commit for an example.
Important: In order to remove a finder, you should ensure there is a clear business requirement in doing so, and that all associated documents have been correctly dealt with - unpublished, redirected, migrated or removed. If the code is not removed from all relevant repositories, there is a chance the finder will be inadvertently republished, for example by republishing all finders. You must therefore make sure the code is removed in order to keep the finder unpublished.
The following steps are required to remove a finder:
-
Unpublish the finder in all environments using the provided rake task:
rake unpublish:redirect_finder["uk_market_conformity_assessment_bodies","https://redirection_link.gov.uk"]
-
Remove usages from
publishing-api
:- Remove the format from this list and this list.
- Remove the field definitions from this file.
- Remove the example from this directory.
- Run
bundle exec rake build_schemas
to regenerate schemas.
See example commit.
-
Remove usages from
specialist publisher
. See example commit. -
Remove usages from
search-api
. See example commit. -
Remove any usages from
finder-frontend
, if applicable. -
Deploy all changes.