% IMPORTANT: The following is UTF-8 encoded. This means that in the presence
% of non-ASCII characters, it will not work with BibTeX 0.99 or older.
% Instead, you should use an up-to-date BibTeX implementation like “bibtex8” or
% “biber”.
@INPROCEEDINGS{Hagemeier:1032450,
author = {Hagemeier, Björn},
title = {{J}upyter4{NFDI} - a central {J}upyter {H}ub for the
{NFDI}},
reportid = {FZJ-2024-06256},
year = {2024},
note = {https://www.youtube.com/watch?v=1pGPJYjs8tQ},
abstract = {Jupyter Notebooks are widespread across scientific
disciplines today. However, their deployment across various
NFDI consortia currently occurs through individual
JupyterHubs, resulting in access barriers to computational
and data resources. Whereas some of the services are widely
available, others are barricaded within VPNs or otherwise
inaccessible for a wider audience. Our ambition is to
improve the user experience by offering a centralized
service to extend the reach of Jupyter to a broader audience
within the NFDI and beyond. This will be facilitated through
two main constituents. Firstly, the technical foundation for
our service will be the versatile configuration frontend
that has been proven to meet user needs for the past seven
years at JSC. It is continuously extended and traces and
ever growing set of backend resources ranging from Cloud
based, small-scale JupyterLabs to full-scale remote desktop
environments on high-performance computing systems such as
Germany's highest-ranked TOP500 system JUWELS Booster. We
envision to extend this approach to various backend systems,
such as the ones provided by the NHR. Secondly, an
integration into the developing IAM4NFDI base service,
facilitating user and community access to the above
mentioned resources. Given the diversity of resources and
their individual policy for user access, a central base
service must support its users in the best possible way to
access only those resources available to them. We plan to
achieve this through appropriate user guidance, including
information about how to apply for resources. Moreover, we
will technically ensure that users can only see and
configure those resources to which they have
access.Importantly, the centralized system will not only
simplify access but also support the import of projects
along with their necessary dependencies, fostering an
ecosystem conducive to creating reproducible FAIR Digital
Objects (FDOs), possibly along with notebook identifiers
supported by PID4NFDI. Our commitment is to a collaborative
and centralized approach that brings Jupyter notebooks
within everyone's reach and democratizes access to the
infrastructures for reproducible computational research
within the NFDI and beyond. In this talk, we'll revisit the
history of the current solution, the landscape in which we
intend to make it available, and give an outlook on the
future of the service.},
organization = {NFDI Talk, online (Germany)},
subtyp = {Other},
keywords = {Jupyter (Other) / FAIR (Other) / NFDI (Other)},
cin = {JSC},
cid = {I:(DE-Juel1)JSC-20090406},
pnm = {5112 - Cross-Domain Algorithms, Tools, Methods Labs (ATMLs)
and Research Groups (POF4-511) / DFG project
G:(GEPRIS)521473512 - Base4NFDI - Basisdienste für die NFDI
(Text plus) (521473512)},
pid = {G:(DE-HGF)POF4-5112 / G:(GEPRIS)521473512},
typ = {PUB:(DE-HGF)31},
doi = {10.5281/ZENODO.14162496},
url = {https://juser.fz-juelich.de/record/1032450},
}