OJS setup, migration, hosting, workflows, reviewer support, indexing preparation and staff training for journals and research institutions.
Discuss your journal ↗Structured moves and new installations with workflow configuration.
Reliable technical care, updates, access support and issue resolution.
Support for OAI, DOI workflows, JATS preparation and metadata quality.
Mamba Technologies supports journals and research institutions with Open Journal Systems setup, migration, hosting and user training. The work connects the technical platform with editorial tasks, author journeys and the quality of published metadata. Journal editors retain responsibility for editorial policy, publication decisions and approval of journal information.
An OJS project starts with the existing journal, its publication history and the workflow the editorial team needs. We review issues, articles, files, user roles and the information that must be retained. For a migration, the source platform and available records determine the transfer approach and the checks required.
A migration plan should identify backups, a review environment, representative records to test and the point at which new changes are paused for the final transfer. The team needs to inspect article details, files, issue organisation and user access before accepting the result. Missing source information cannot be assumed to appear automatically in the new platform.
Journal support can include configuring agreed roles, submission instructions and the stages used by the editorial team. Training should follow practical tasks for editors, reviewers and administrators. Clear instructions help reduce confusion when authors submit files or reviewers need to find an assigned task.
We can also scope support for metadata quality, DOI-related workflows, OAI arrangements and XML preparation where the project requires them. These are distinct activities and depend on the journal’s setup and external service requirements. Technical preparation does not guarantee acceptance into an index, directory or repository; those decisions belong to the relevant organisation.
A journal platform needs a maintenance plan that considers its files, database, extensions, backups and administrative access. Updates and configuration changes should be assessed against the installation in use. Access and publication problems need a clear support route so editors know where to report an issue and what information to include.
For an OJS proposal, share the current platform, approximate archive size, required changes and whether the journal is moving providers. Include the main difficulties faced by editors and authors. We can then separate setup or migration, training, ongoing care and any specialist metadata work into a clear scope.
No. Platform setup and metadata preparation can support an application, but indexing organisations apply their own criteria and make their own decisions. Editorial quality and journal policies remain the responsibility of the publisher and editorial team.
Yes. We first assess the source records, files and target installation. The scope should include mapping, transfer checks and editorial review of representative articles and issues before the migration is accepted.
Yes. Sessions can follow the journal’s agreed submission, review and publication process, with separate guidance for administrators where required. Training materials and follow-up support are specified in the proposal.
MAMBA TECHNOLOGIES