Problem: this project can't replace RDSS's fork yet

[sevein]

RDSS wants to switch to vanilla AM but it can't because the issues listed below haven't been addressed yet.

Similar issue in SS: artefactual/archivematica-storage-service#375.

Dependencies:

• Parent to Problem: can't build MCPServer from Dockerfile #1124 (PR Docker: use Debian jessie base images #1154).
• Parent to Problem: email settings are not configurable #1128 (PR Set up email settings via config #813).
• Parent to Problem: job status field in Dashboard reads unexpected ID value #1130 (PR Dashboard: show job status instead of id #1155).
• Parent to Problem: install's command fails when the superuser exists #1131 (PR Make installer idempotent #1165).
• Parent to Problem: metadata reingest fails when dc:type is null #1132 (PR Exclude empty dublin core elements #1168).
• Parent to Problem: install's command is not idempotent #1134 (PR Make installer idempotent #1165).
• Parent to Problem: processing of datasets containing no files stalls at the end of the Transfer stage  #1135 (PR Add checks for empty transfers #1167).
• Parent to Problem: processing configurations can't be reset #1138 (PR Allow users to reset processing configuration #1166).
• Parent to Problem: AM doesn't have a notion of public URL #1140 (PR Add site_url setting #1142).
• Parent to Problem: SS client timeout setting for async API endpoints is missing #1133 (PR storageService: add new query timeout #1170).
• Parent to Problem: processing is aborted after failure in Index AIP #1136 (PR MCPClient: add indexAIP error handling #1190).
• Parent to Problem: start transfer API endpoint is blocking #1139 (PR Add /api/v2beta/package endpoint #1191).
• Parent to Problem: can't set custom premis agent version number in qa or dev environments #1192 (PR Dashboard: set_agent_code command #1193).

Lower priority:

• Parent to #1137 - not in AM18 roadmap yet.
• Parent to #1129 (PR Make sure transfer names can begin with dash #1169) - needs more work.

Related: https://jiscdev.atlassian.net/browse/RDSSARK-521.
Fork's address: https://github.com/JiscRDSS/archivematica.

[joel-simpson]

Regarding RDSS version number (JiscRDSS#48, JiscRDSS#51)
I agree, since the goal is for Jisc to be able to replace their fork with the public release of Archivematica, the RDSS version number is not as important as it was.
However, the RDSS version number is associated with the rdss-archivematica repo, which is a sort of 'distribution repo'. An RDSS version number is associated with a version number for each component; including Archivematica, the storage service, channel adapter, NextCloud and others. This is very useful for a managed service provider with many deployments.
It could well be an acceptable trade-off to lose this (as part of migrating back to the public release and not having a Jisc fork).
On the other hand, if we could find a way to include both version numbers, I think it could benefit many other users. Perhaps it would be possible to have an optional "distribution version number" (or "deployment" or similar)? This wouldn't even need to be used in the METS as an agent, and could be purely for support purposes.