Drupal-based knowledge archive network (DKAN) Data Portal Upgrade - MIGRATION

Drupal-based knowledge archive network (DKAN) Data Portal Upgrade - MIGRATION
Consultants to upgrade all the DKAN data portals deployed through the Inform project (19 in total) from Drupal 7 to the latest stable Drupal 9.
The upgrade should retain the current user workflows as much as possible and ensure that all content and portal themes are ported over to the upgraded system; and to ensure that the final product meets the specifications and expectations as well as providing the ability to make additional improvements.
The successful applicant will need to provide services as required over a period of 4 months basis and a following 6 months on a retainer basis.

EVALUATION CRITERIA
Experience with Drupal 8 and Drupal 9 (site building and module development) – 20%
6.2. Experience in systems analysis – 15%
6.3. Experience with data migration – 10%
6.4. Experience with the DKAN data management platform – 20%
6.5. Development workplan and schedule of activities – 15%
6.6. Demonstrated experience supporting a network of linked databases. – 5%
6.7 Experience working in the Pacific region with other organisations

Scope of work
Review systems specifications and recommend changes as necessary
•Use the git repository provided by SPREP for deployment (Gitlab)
• Track progress using issue trackers for managing updates/features (Gitlab tickets)
• Ensure that deployment is compatible with the current workflow using Docker
• Preference: Integrate automated testing for CI/CD in the workflow • Do not use any deprecated functions to improve portability to Drupal 9
• Ensure development environment is compatible with docker4drupal (see Preferred software stack)
• Current user workflows should be retained or similar enough not to require additional training – content management and user management
• SOLR based search should be implemented in upgraded Drupal 9 DKAN
Regular user acceptance testing (with Inform project team)Structure repository to be open source
• Migrate existing data over to the upgraded Drupal 9 DKAN (Deliverable 3)
• This should include datasets, resources, data stories, data dashboards, groups, and basic pages
• Assistance with updating existing help material for the data portals (Deliverable 6)
• Support SPREP team and existing users through the deployment of the upgraded data portal software (Deliverables 7 and 8)
• Existing themes should be ported to the upgraded DKAN data portals (Deliverable 2)
• Existing data harvest workflows should be ported (Deliverable 4)
• API should be provided to ensure that data can be harvested and published to ensure existing linkages to other portals and sites are intact
Deliverables:
1. Upgraded DKAN from Drupal 7 to Drupal 9
2. Current radix-based themes are ported to Drupal 9 DKAN
3. Successful data migration from current DKAN to upgraded Drupal 9 DKAN
4. Data harvesting is successfully setup between Drupal 9 DKAN instances and other sites. This should include a harvest feed (data.json)
5. Upgraded Drupal 9 DKAN uses SOLR search
6. Documentation on the technical architecture of the final system
7. Report on user experience from member states after soft launch
8. Handover training and end of contract report

Timeframe
• 8 weeks of development over a 4 month period.
• Plus, an additional 4 weeks of development over a 6 month period to address user feedback, bugs, and feature requests post-launch.

Skills Required
• Systems Analysis
• Programming
• In-depth knowledge of Drupal 8 or later preferred
• Working knowledge of DKAN or data catalogue systems
? Working knowledge of metadata standards

Reference Links
Latest stable Drupal 9 - Docker using:
• ---------- stack (PHP 7.3 or later)
Gitlab as the platform for git version control system and issue tracker

Reference Links
Example upgraded DKAN instance
• ----------

Example DKAN Data Catalogues
----------
----------


Work Arrangements
This work is expected to be delivered remotely. The workplan will be divided into segmented deliverables (see Deliverables) made up of individual development tickets. The progress of the tickets will be tracked on Gitlab and will be assessed by the Inform team on a regular basis (weekly or as the tickets are completed). The Environmental Information Systems Developer and Analyst (EISDA) will work closely with the consultant to ensure that deliverables meet the required specifications and will also be managing the contract. No travel is expected.