Next: Meeting October 5, 2022 Up: Meeting September 28, 2022 Previous: Meeting September 28, 2022 Index
- Helmholtz proposes to explore OpenProject.
- 'At DESY we have the agreed-upon decision to introduce MS Project Online
as the means for all project planning in the future. This is an IPP
activity and IT is not involved in it (apart from providing infrastructure
services).'
'There is currently no alternative for resource planning available. IT has proposed to have a DESY wide activity to find a solution for this void and to open up access to ATLASSIAN cloud to those groups who wish to continue using Jira on a pay-per-use basis. This will be part of the report to the CCB and if agreed upon, to subsequent advice to the directorate.'
...'We looked at many open-source and commercial tools and homed in on XWiki. It is an open source enterprise Wiki that has been around for a long time, it is commercially supported by at least two companies and it has had a focus on being the open source replacement for Confluence for at least two years now. This has resulted in the development of migration tools and procedures that allow for minimal-loss, maximum-automation conversions. The current migration tool will scan your active Confluence space, determine which macros and plug-ins are in use and will report on missing functionality and propose alternatives. Then it will migrate all content (including attachments etc) into XWiki and give a report on warnings or errors. Should it become clear that spaces are using functionality that is not available in XWiki, there is a strong commitment on the part of the companies to implement an equivalent (on a paid-for basis, of course). All developments are then included in the migration tool and standard Xwiki functionality.'... ...'Gliffy is embedded in XWiki as it is in Confluence. User reports from institutions that have migrated already explicitly mentioned 'no problems' in this area.'... XWiki: 'start user tests in December, production in 2023 in time for a complete migration' before confluence eol.
The scripts for dataset and proposal ingestion are available.
- Kafka vs. inotify - ingestor runs on beamline or core file system - SciCat instances per beamline or one for all - ingest datasets after each scan or once for a beamtime - ingest metradata before StartBeamtime
- proposal ingestor triggered by StartBeamtime - dataset ingestor runs on beamline fs - datasets are ingested after each scan - one SciCat instance for FS - sort-out some details then ask P08 to make tests