uk: Комп'ютерні науки

description: Learn how Radiofrance leverage open-source software to transport, encode, deliver and monitor audio stream in the cloud. You will get a global infrastructure overview on a platform that serve audio stream at scale. What we will talk about: - How we chose our audio streaming protocol (HLS and Icecast). - How to transport audio from corporate SI to the cloud with the protocol SRT. - How we use Liquidsoap as streaming server to implement high availability logic, encode and mux our stream. - How we monitor our system with Prometheus and Grafana. - How to scale an audio streaming platform for 80 radios and 200K+ concurrent listeners.

uk: вхід без авторизації

name: Building an Open-Source based audio streaming platform


Siegfried Kiermayer

type: Person

cs: Informatika

de: Informatik

fi: tietojenkäsittelytiede

uk: Комп'ютерні науки

en: Computer Science

fr: Informatique

da: Datalogi

es: Ciencias de la Computación

nl: Informatica

cs: Technické vědy

de: Ingenieurwissenschaften

fi: tekniikka

uk: Інженерія

en: Engineering Sciences

fr: Ingénierie

da: Ingeniørvidenskab

es: Ingeniería

nl: Engineering

description: My team build a new Closed Build Environment for building Release Packages on Google Cloud Platform(gcp) with Google Kubernetes Engine (GKE). I like to take you on a small journey through a variety of topics we came across (open for change): How we bootstrap and how we use ArgoCD Autoscaling to 100 Build nodes for building Why we are using Prometheus-Operator SRE or how we maintain our stack Product aspect Base Image building & scanning Network setup with Shared VPC Google Cloud Platform IAM Permissions vs. RBAC Specific GKE Features like Workload Identity And others Simple real live example how my team is doing it. Looking forward to inspire and to get feedback from others!

TIB AV-Portal

type: Service

type: WebContent

type: MediaObject

@language: en

cs: přihlášení není vyžadováno

de: keine Anmeldung erforderlich

uk: вхід без авторизації

en: no login required

nl: geen login vereist

name: Our road to a k8s/GKE based Closed Build Environment: A small journey to an autoscaling build env based on Jenkins.

FOSDEM VZW

type: Organization

cs: Video

de: Video

fi: Video

uk: Відео

en: Video

fr: Vidéo

da: Video

nl: Video

es: Video


uk: Комп'ютерні науки

description: A talk about how OpenBeans, an Apache NetBeans IDE distribution was possible due to pkgsrc, the NetBSD package management framework. OpenBeans IDE started in Nov 2018 under the name CoolBeans. This was an Apache NetBeans IDE 'distribution' which repackaged the Apache NetBeans modules, plus some other modules that were still not available yet (such as the C/C++ support modules, JavaEE modules, native notifications on macOS/Windows, etc). CoolBeans was open sourced under the plain ISC license under the OpenBeans name. OpenBeans produces Windows installers as well as macOS disk images for end users. It does this using pkgsrc from NetBSD, which seems to be a very good match for distribution-like projects.

uk: вхід без авторизації

name: OpenBeans IDE - Creating an Apache NetBeans Distribution


Apache OpenOffice Buildsystem

uk: Комп'ютерні науки

description: This talk will be about the OpenOffice Build system. We will talk about how it works today's, issues with it. And the talk will highlight current development in this field plus where it might moves in the future. (plans of development) Sheduled length will be 20 min +question Currently the build system is a mixture of dmake, gmake, ant and other tools. After a short going through I like to describe the vision we have for the future build system we are working towards.

uk: вхід без авторизації


uk: Комп'ютерні науки

description: Progressive Delivery makes it easier to adopt Continuous Delivery, by deploying new versions to a subset of users and evaluating their correctness and performance before rolling them to the totality of the users, and rolled back if not matching some key metrics. Canary deployments is one of the techniques in Progressive Delivery, used in companies like Facebook to roll out new versions gradually. But good news! you don't need to be Facebook to take advantage of it. We will demo how to create a fully automated Progressive Delivery pipeline with Canary deployments and rollbacks in Kubernetes using Jenkins X, an open source platform for cloud native CI/CD in Kubernetes, and Flagger, a project that uses Istio and Prometheus to automate Canary rollouts and rollbacks.

uk: вхід без авторизації

name: Progressive Delivery: Continuous Delivery the Right Way


uk: Комп'ютерні науки

description: See how Red Hat’s CKI project uses GitLab CI to test kernel patches as soon as they're posted to maillists. Red Hat's CKI project uses GitLab CI to organize and track its pipelines, lint, patch, and build Linux kernels, and oversee testing. It also uses a number of supporting systems to discover kernel patches and commits, maintain hardware inventory, provision hardware and VMs, run tests, and finally record and report results. See which tricks the project is pulling to tie all these parts together, and test patches posted to several maillists, commits to 15+ git repos, builds done by other build systems, as well as weird things like stable kernel patch queue, and parts of its own software stack. Making such extensive use of a CI system inevitably uncovers its limitations, and a list of these will also be presented along with some possible solutions.

uk: вхід без авторизації

name: Abusing GitLab CI to Test Kernel Patches


uk: Комп'ютерні науки

description: Lukas Vrabec built a new standalone tool, udica, for generating SELinux policy profiles for containers based on automatic inspecting these containers. We will focus on why udica is needed in the container world and how it can make SELinux and containers work better together. We will show real examples where SELinux separation for containers had to be turned off because the generic SELinux type container_t was too tight. With a tool like “udica”, users and developers can easily customize the policy with limited SELnux policy writing skills. Come to see how easy also you can create custom SELinux policy for your containers! This talk will explain how SELinux works with containers. We will show how to enable/disable SElinux using multiple different container runtimes and define the default types. One issue with these types is that they are tough to customize. The two default types for running containers are containert which is a fully confined domain, which eliminates any use of the host files unless they are relabeled. Or spct, which is the type containers run with when SELinux is disabled for container separation, --privileged mode. As an example, If you had a container that you wanted to be able to gather the logs from /var/log on the host and send them to a centralized server, you have to disable SELinux separation. Writing custom policy for each container that needed additional access would be very difficult and require a container policy writer.

uk: вхід без авторизації

name: Using SELinux with container runtimes: Because privileged containers are scary


uk: Комп'ютерні науки

description: Overview of SUSE's Linux kernel testing in OpenQA, how we keep track of known issues, explore test results and other features of JDP. The JDP framework is written in Julia, uses Redis as a distributed data cache and Jupyter for interactive reporting. OpenQA is a large application used for testing operating systems and displaying the results.

uk: вхід без авторизації

name: OpenQA with JDP (Julia): Operating system testing and result analyses


uk: Комп'ютерні науки

description: Overview of the process the OpenStack community uses to manage all software releases through automation around Git commits. The OpenStack community has enabled a lot of automation around releasing their software. This presentation will give an overview of how code reviews are used to manage release activity. It will step through the use of Zuul CI jobs to perform validation of requests before they are accepted, and how commits are used to trigger jobs to tag and release the software, update documentation, trigger requirements updates, and other follow on work that needs to happen whenever new code is released.

uk: вхід без авторизації

name: Releasing Software with GitOps: How OpenStack manages releases using Git based automation


VUOS: Give Your Processes a New VU

uk: Комп'ютерні науки

description: VUOS is a different perspective on namespaces, anykernels and related concepts. The main idea behind VUOS is that it is possible to give processes their own "view" using partial virtual machines. A partial virtual machine intercepts the system call requests and operates like a filter: system calls can be forwarded to the kernel of the hosting system or processed by the partial virtual machine hypervisor. In this way processes can see a mix of resources provided by the kernel (on which they have the same view of the other processes) and virtual resource. It is possible to mount filesystems, load networking stacks, change the structure of the file system tree, create virtual devices. The hypervisor is just a user process so while it gives new perspective for processes, it does not widen the attack surface of the kernel.

uk: вхід без авторизації


uk: Комп'ютерні науки

description: WebRTC is showing up in many places: security cameras, babymonitors, games streaming, autonomous cars etc I'll describe the advantages of WebRTC in these devices but also the challenges of non-mainstream usage. I'll bring a demo or two and some sample code.

uk: вхід без авторизації

name: WebRTC isn't just for (video) conference calls


uk: Комп'ютерні науки

description: YottaDB is a mature, hierarchical key-value, free / open source NoSQL database whose is used in enterprise-scale mission-critical applications in banking and healthcare, and also scales down to fit on IoT devices like the Raspberry Pi Zero, as well as applications in-between (like the University of Antwerp library catalog system). When a customer funded us to develop a Go API to YottaDB, we thought it would be a straightforward project. But it was a very painful exercise for us. The presentation discusses the problems we faced, and how we overcame them. Go is a popular language for writing highly concurrent software, and works well when used in isolation. Using Go alongside software written in other languages (such as C) can be done, but there are some hidden dragons to keep an eye out for. In addition to obvious problems, such as calling C variadic functions, other more subtle problems are hidden deep in the depths of Go documentation. Consider callback functions; how does one pass a function pointer from Go to C to provide a callback? There are strict limitations enforced by Go on what pointers may be passed to C routines, intended to prevent faults resulting from Go structures being garbage collected without knowledge of the C code. Without being able to pass pointers, even function pointers, how do we “pass” a callback function to the C code to callback into? Furthermore, how do we pass data to the callback function, since we can’t pass Go structures? Given that we can’t pass Go structures to C code, at some point we will need to allocate C structures to store data for the C code to operate on. Go promises one thing about memory allocated in C land; it will not keep track of it for you. The garbage collector will gladly clean up any Go structures no longer needed, but will not clean up the associated C memory. How can one write code which isn’t likely to result in memory leaks, using this model? Perhaps the most difficult challenge to overcome is that Go makes no promises about what thread is running code. Go does its best to hide the identity of Go routines from the user, so they won’t rely on this metadata for handling code execution. This presents a problem for many C applications, which often use POSIX mutexes to control access, and the owner of a mutex needs to belong to a specific thread. How can one write Go applications that allow the concurrency Go users expect, without trashing the libraries they are calling? Of course, none of the solutions we talk about here are any good unless you can compile your program. The hidden dragons of Go also lurk behind the “go build“ command; fitting in the required C flags requires knowledge of, among other things, pkg-config, a systems tool used behind the scenes by programs like CMake and autotools. We had to tackle all these problems, and many more, during the development of the YottaDB Go wrapper. This presentation hopes to pass some of our hard-learned lessons to other programmers who will use Go to interface with non-Go libraries and utilities.

uk: вхід без авторизації

name: Hidden Drangons of CGO: Hard-learned Lessons from Writing Go Wrappers


Lightning talk session

uk: Комп'ютерні науки

description: Hallot, Olivier - Help editing with the new XHP editor Koese, Guelsah - Improving interoperability in Libre Office Schubert, Svante - Disruption Warning! Saunders, Mike - OpenBadges for the LibreOffice community Christener, Nicolas - LibreOffice IOS App Behrens, Thorsten - Dogotal Signatures in Okular

uk: вхід без авторизації


Functional Programming with Go

uk: Комп'ютерні науки

description: Are you tired of seeing Object Oriented code everywhere, with mutations, side-effects and headaches? Luckily, writing Go does not have to be that way! Functional programming is perfectly possible within Go, hence we can leverage FP techniques to make our code more robust, testable and fun. Functional Programming in Go Go is a multi-paradigm language, yet most code you encounter ‘in the wild’ is written in a mostly Object-Oriented way. Yet, Go allows us to write code in a functional way as well, which offers certain advantages over a more traditional “OO” approach. What follows in this description is also the general flow of how it will be presented. What is FP? First we’ll start by defining what we mean by functional programming. Superficially Go might not look like what you expect a functional language to look like. But we’re really just missing the syntactic sugar here, as a lot of the underlying concepts that are central to Functional Programming are reflected in Go. Hence it is important to take a look at what many programmers consider requirements for being “functional” such as: Higher-order functions, recursion (with tail-call optimization), purity, idempotence, .. and how these requirements are met (or aren’t met) by Go. How to leverage them in Go Once we have convinced ourselves that Go gives us the building blocks for writing FP code, we’ll dive into some concrete examples of what we can do with Go. We’ll look at function currying, continuation-passing style programming, pure functions, recursion (without TCO), monads and more. It’s important to highlight here why we want to use these constructions and when. At best case, you’ll learn how to leverage them in your own codebase. At worst, you’ll have seen some cool things with Go. Don’t be put of if you don’t know these terms yet, we’ll start with the easy concepts you’ve probable already used such as recursion, and work our way up to the complexer ones. Using libraries Go actually has libraries that provide an API for programming in a more functional style. We’ll give them an honorable mention but they won’t be the focus of the talk, as you can get started easily without them. But, they do offer certain things we “miss” in Go by default (like Generics). Benefits Writing Go code in this style has numerous benefits over our traditional approach. My goal of this talk is not just to show you cool things you can do with Go, but also why you want to them. You’ll also see introducing them to an existing codebase is easy, and that FP is really not as scary as it might sound! Downsides Using this style of programming is not entirely a walk in the park. There’s a price to be paid for writing functional code in Go, the main one will be that you’ll take a performance hit. But the performance hit might not be where you expect it! Functional programming is one tool in your toolbox, it’ll greatly empower you to solve certain problems, whilst it’ll help you shoot yourself in the foot for other problems. Bonus benefits! Yes, you’ll even take away something from this talk you might not have expected! A lot of people think of Haskell when they hear functional programming. Which might have scared them away from functional programming. In this talk you’ll get a look at functional programming with a familiar syntax and a language you already love. This will help you understand the underlying concepts and see how they relate to Haskell and other functional languages, where the syntax might be a bit different but the idea remains the same. Do I need prior knowledge of FP? No, absolutely not! You don’t need to have done functional programming before to benefit from this talk. There are concepts for all levels of understanding of functional programming. If you don’t know anything about functional programming yet, you’ll discover it in this talk. And if you’re already an FP-wizard who dreams in Haskell, you’ll learn how to transfer that understanding to Go.

uk: вхід без авторизації


uk: Комп'ютерні науки

description: The talk will give a general overview of the Liquidsoap language, and put focus on recent new features: support for HLS, efficient video, etc. The task of generating multimedia streams such as for webradios or live youtube channels is a complicated task. One needs to face low-level issues (properly encoding and distributing the streams), mid-level issues (performing normalization, signal processing, color grading, etc.) and high-level issues such as generating the stream from a wide variety of sources (local files, other streams, live interventions, user requests, etc.) and properly combining them (performing transitions, adding commercials, vary the contents during the day, etc.). In this talk, we present Liquidsoap, a dedicated high-level functional language, which allows performing all these tasks in a modular way, with strong guarantees that the stream will not fail on the long run.

uk: вхід без авторизації

name: Functional audio and video stream generation with Liquidsoap


uk: Комп'ютерні науки

description: How does one manage and document change in Python projects, be that new features or deprecation or removal of a feature? Let's explore some of the tools a Python developer can keep in their toolbox for just this purpose. Software rarely stands still (unless it's TeX). Things are added, things are removed, things break and are then hopefully fixed. Managing this, from both the developer and user perspective, can be tough. In this talk we examine and compare some of the tools that one can use to make this process easier, such as 'debtcollector', 'reno' and 'towncrier', and contrast these with alternatives used in other projects. This talk would mainly be of interest to developers of open source libraries, though the same tooling can be used for any Python library or application that wishes to maintain stable interfaces and/or document changes in their product.

uk: вхід без авторизації

name: Will somebody *please* tell me what's going on?: Managing change in Python projects


Pythonics monads

uk: Комп'ютерні науки

description: In this talk I would give some motivating examples behind the idea of monads in Python, and show some implementation examples. I'd also show how we can leverage AST transformations to make the Python syntax more amenable to the use of monads. I have already given a talk on this topic during Pycon France 2018 in Lille. Unfortunately, the video footage has been lost, but the original slides can be found here: https://slides.com/v-perez/pythonic-monads-in-real-life#/ If this talk was selected, I'd probably update it a bit to account for the feedback I received, and new ideas I may have. In this talk I would give some motivating examples behind the idea of monads in Python, and show some implementation examples. I'd also show how we can leverage AST transformations to make the Python syntax more amenable to the use of monads. I have already given a talk on this topic during Pycon France 2018 in Lille. Unfortunately, the video footage has been lost, but the original slides can be found here: https://slides.com/v-perez/pythonic-monads-in-real-life#/ If this talk was selected, I'd probably update it a bit to account for the feedback I received, and new ideas I may have.

uk: вхід без авторизації


uk: Комп'ютерні науки

description: repcloud is a tool for repacking postgresql databases in cloud written in python3. repcloud is a tool for repacking postgresql databases hosted in cloud. as pgrepack is a far better approach for repacking tables online, there are situations where is not possible to install the extension on a postgresql if it's hosted in cloud (e.g. Heroku). Hence comes repcloud which can help in rebuilding the tables on line with the use of simple SQL and some postgreSQL magic. The author will explain how the project started, the functionalities and the limitations.

uk: вхід без авторизації

name: repcloud: A repacker for PostgreSQL in cloud


uk: Комп'ютерні науки

description: While working on the Mercurial version control system, we hit our heads against the limits of Python's performance. In this talk we will see how Python and Rust can cohabit to play off of each other's strenghts to improve a big open-source project, and what advances have been made in bridging the two languages.

uk: вхід без авторизації

name: Boosting Python with Rust: The case of Mercurial


uk: Комп'ютерні науки

description: From my talk you will learn about some lesser-known features of sudo, and how you can make your security more flexible by extending sudo using Python. Everybody knows sudo, right? Sudo allows a system administrator to give certain users the ability to run some commands as root, while logging the executed commands and their arguments. It is installed by default on almost all Linux systems, and is available for most commercial UNIX systems. Sudo allows you to fine-tune access policies, record sessions, and do extensive logging. Still, even system administrators often only know it is the “prefix” to use before entering a command requiring root privileges, and don’t realize its true powers. Did you know that with version 1.8 sudo changed to a plugin-based architecture? You can extend or even replace basic functionality through plugins. While plugins provide the ultimate flexibility – and there are both open source and commercial plugins for sudo available – it is not easy to extend sudo. This is why the Python plugin is under way to sudo (and will be released before FOSDEM). Sudo has a number of well defined APIs for plugins (https://www.sudo.ws/man/sudo_plugin.man.html). The Python plugin builds on these APIs. For example, you can set your own policies using the policy API, or access what is happening on the screen using the I/O API (used by session recording). Using Python for extending sudo makes development not just easier (no development environment necessary), but opens up many new possibilities. For example, you can develop a plugin which analyzes on-screen activity in real-time, and breaks the session if the infamous “rm -fr /” command appears on screen. As multiple I/O plugins can work in parallel, you do not have to give up session recording to analyze sessions in real-time from Python. From my talk you will learn about some lesser-known features of sudo, and how you can make your security more flexible by extending sudo using Python.

uk: вхід без авторизації

name: Extending sudo in Python: Best of both worlds


uk: Комп'ютерні науки

description: Correlation Analysis is a statistical method that is used to discover if there is a relationship between two variables, and how strong that relationship might be. A correlation coefficient is a numerical measure of such correlation. According to the Cauchy–Schwarz inequality it has a value between +1 and −1, where 1 is total positive linear correlation, 0 is no linear correlation, and −1 is total negative linear correlation. One of the axioms of automated testing is that tests are independent and in spite of that correlation coefficient should be equal to 0. But often it isn't. In this work, we are going to present a method of evaluation of tests suites quality based on correlation coefficient and finding their weak points. Using PC Engines open-source firmware regression test results, which are based on over 140 automated tests run with 2 flavors of software on 4 different platforms, we will show how its quality can be described numerically, and how that results can be used to optimize test criteria. As far as automated testing is considered all the tests can have only two expected output values - pass or fail. Originally Pearson's correlation coefficient is the covariance of the two variables divided by the product of their standard deviations - the first question was how to do it for Boolean variables. We assumed that the only value that matters can be a failure of a test. During the lecture, we will present how mathematical analysis can reveal potential flaws in test criteria by targeting cases that have a large chance to fail simultaneously.

uk: вхід без авторизації

name: Correlation analysis in automated testing


Container Live Migration

uk: Комп'ютерні науки

description: The difficult task to checkpoint and restore a process is used in many container runtimes to implement container live migration. This talk will give details how CRIU is able to checkpoint and restore processes, how it is integrated in different container runtimes and which optimizations CRIU offers to decrease the downtime during container migration. In this talk I want to provide details how CRIU checkpoints and restores a process. Starting from ptrace() to pause the process, how parasite code is injected into the process to checkpoint the process from its own address space. How CRIU transforms itself to the restored process during restore. How SELinux and seccomp is restored. I want to end this talk with an overview about how CRIU is integrated in different container runtimes to implement container live migration.

uk: вхід без авторизації


uk: Комп'ютерні науки

description: Almonit is a project for decentralized websites and web services. Decentralized websites and web services are an alternative to the way the web functions today. They combine decentralized storage (like IPFS), decentralized name services (like ENS) and P2P networks in order to replace the server-based model of the web. This lecture describes the Almonit project, its architecture, the technical details of the technology and the ecosphere in which it is created. Come discover the state-of-the-art of this up-and-coming area! This talk has been accepted late, due to Open and federated identities with ID4me by Vittorio Bertola being promoted to a full talk at 11:00. How does the web function? Generally speaking, it uses servers to provide content or services, and DNS to provide access to those servers. The Almonit project provides an alternative to the traditional server-DNS model. Instead of a server, we use decentralized storage (like IPFS), and instead of DNS, we use a decentralized name service (like ENS). We provide tools, methods and a portal for creating and accessing the decentralized web. The decentralized websites and web services scene is very new. In its current form, it was developed mostly in 2019. So far, it contains a few dozen websites experimenting with the technology, but its potential is promising. We envision it being used to create community-driven websites which would be made, moderated and maintained by a community instead of a central entity. This lecture describes the Almonit project, its architecture and technical details. We also present the ecosphere of decentralized websites and web services in which the project is created, and survey the past, present and also possible future use-cases of this technology, including its limitations.

uk: вхід без авторизації

name: Almonit: Decentralized Websites and Web Services


uk: Комп'ютерні науки

description: Avoiding repressive surveillance, circumventing censorship and protecting privacy can become a complicated and costly challenge. Many of the available alternatives do not completely solve the problem of trust, centralization of information and dependency on whoever is offering the services to us. Initiatives that offer alternative tools often become targets of censorship and repressive surveillance. Others do not include all the services the community needs, or require a minimum of technical knowledge, forcing organizations to continue using applications offered by third parties or renounce them. MaadiX is a solution that reverses this imbalance in favor of users, giving them back control over their communications and data, as well as over all the applications they need in order to process them, facilitating the technical adoption and maintenance of server-side, privacy-oriented, secure, and censorship circumvention technologies. MaadiX provides one click installation of advanced free and open source applications such as email server, mailman 3, openVPN, RocketChat. Owncloud, Nextcloud, OnlyOffice. Libre Office Online among many others, on remote or local private servers, without the need to have access to their system and data, and providing updates and technical support. MaadiX acts as a repository of 'recipes' that provides all the instructions and commands needed to automatically install and configure applications from a graphical interface. The catalogs are served through Puppet modules but we've changed the way these technologies works, improving them in order to avoid creating yet another centralized google-like model and avoiding having access to users' systems and data. MaadiX has been reviewed by external security auditors. We would like to dicuss with the audience how to better deal with the balance between security and usability and share how MaadiX works as well as which community is actually around the project or is using it.

uk: вхід без авторизації

name: MaadiX, your cloud in your hands: Tool Kit and Graphical interface for VPS management


uk: Комп'ютерні науки

description: Society is becoming increasingly more aware of the importance of protecting digital information and it is becoming clear that the current centralized model has came to an end. The future of the Internet is distributed. Unsupervised, unmoderated access, affordable storage, data-replication, and security and privacy built-in are the most important aspects of the Internet of the future. Unfortunately, a global, reliable, decentralized network cannot be built without actual physical nodes, as the opposite of thousands of nodes in centralized cloud data center. Only by building an open network of physical nodes we can pave our way as a society to the decentralized Internet of the future. Identity Box is a personal P2P networking device giving you access to a global network of distributed storage, digital identity, and distributed personal apps. It is a community effort of building the next-generation, decentralized infrastructure that enables an open platform for privacy-preserving ecosystems. Most of the data today belong to just a handful of companies. Personal documents, photographs, videos, things that we put online in general, contain lots of sensitive information. Information that we would rather prefer to stay private. Very often the same companies that provide more or less "complimentary" storage space for our disposal, also help us managing our whole digital existence. The combination of the data and the identity information is a powerful combination which empowers well-established business models where the user's data or the user itself become a product. Allowing sensitive data to be kept by well-known service providers makes it easier than ever for illegal institutions, but also the state, to gain insights into the data that they have no rights to access. Our sensitive personal data are kept by the state, healthcare organizations, financial institutions, and corporations. We do not have control over these data and our access to them is limited. Every institution storing the data has not only its own policies, but also uses proprietary technologies to access the data. These data silos make interoperability hard and give institutions almost complete freedom to use the data without consent of the user. Society is becoming increasingly more aware of the importance of protecting the digital content and it is becoming clear that the current centralized model has came to an end. The future of the Internet is distributed. Unsupervised, unmoderated access, affordable, unlimited storage, security and privacy built-in are the most important aspects of the Internet of the future. Unfortunately, a global, reliable, decentralized network cannot be built without actual physical nodes, as the opposite of thousands of nodes in centralized cloud data centers. Users need to be re-introduced to the concept of decentralization and learn the advantages of technologies like self-sovereign identity, and content-addressable networks. Only by building an open network of physical nodes we pave our way as a society to the decentralized Internet of the future. Building the decentralized Internet of the future is therefore a community effort, where all participants become the actual owners of the distributed global infrastructure. To support this community movement, we propose Identity Box: a personal P2P networking device giving you access to the global network of distributed storage, digital identity, and distributed personal apps. Identity Box is a physical device, but at the same far more than just piece of hardware. Together with the included software and Identity App, Identity Box enables an ecosystem of rich, distributed personal applications. It supports IPFS, Self-Sovereign Identity, and end-to-end encrypted storage. And that's just the beginning. Join us in building the decentralized Internet of the future!

uk: вхід без авторизації

name: Identity Box: Decentralized Web of the Future


uk: Комп'ютерні науки

description: Push messages are an essential part of connected mobile devices. They are also one of the critical missing pieces in the open source Android ecosystem. Until now, free Android apps would either need to implement their own push notification system, do without any push messaging or use the proprietary Google Cloud Messaging service. In this talk I will introduce OpenPush, a free and open source, self-hosted and decentralized replacement for Google Cloud Messaging. We expect both a long battery life and instant notifications from our mobile devices. When implementing your own mobile push functionality you can usually optimize for either of these goals. This is especially true if the user is running multiple applications which each come with their own persistent on-going connection for push notifications. Wanting to combat the battery drain associated with maintaining multiple connections Google introduced the Google Cloud Messaging (GCM) framework which recently has become Firebase Cloud Messaging (FCM). Firebase Cloud Messaging relies on the availability of the proprietary Google Play Services Framework on an Android device. Using FCM also requires the inclusion of the proprietary FCM client library into open source Android apps like Signal, Wire or even Firefox, which makes them effectively non-free software which cannot be distributed via the fully free F-Droid software repository. Additionally all push notifications delivered via FCM need to pass through Google's servers leaving a metadata trace, even if it's an empty wakeup event or if the content of the message is encrypted. Decentralized, self-hosted systems like Matrix, Nextcloud or RocketChat currently still have a dependency on Google's infrastructure and Terms of Service for delivering push Notifications. In this talk I'll present a self-hosted, free alternative push messaging implementation which can either run alongside or as a replacement to FCM. The talk will give a general architecture overview as well as walk through the design and implementation challenges of a push messaging service. Further I'll present how OpenPush can be used by different projects and discuss some additional ideas on how the wider ecosystem could look like in the future.

uk: вхід без авторизації

name: OpenPush: Introducing a Free, Decentralized Push Messaging Framework for Android


PipeWire in the Automotive Industry

uk: Комп'ютерні науки

description: PipeWire has recently been adopted by Automotive Grade Linux for its implementation of the low-level platform audio service, replacing entirely previous solutions. Getting there had, of course, many challenges. In this talk, George is going to talk about how PipeWire has managed to overcome these challenges and has evolved to support automotive use cases and hardware through the design and implementation of a new, reusable, session & policy management component, WirePlumber.

uk: вхід без авторизації


uk: Комп'ютерні науки

description: There is increasing interest to apply graph analytical techniques to a wide array of problems, many operating on large-scale graphs with billions of edges. While graph algorithms and their complexity is textbook material, efficient implementation of such algorithms is still a major challenge due to a number of reasons. First, the irregular and unstructured nature of graphs leads to a massive amount of random data access, which makes it difficult to use typical caching and parallelization techniques. Second, to optimize their code, developers need to be aware of the nuances of the underlying hardware which, at the very least consists of multiple CPU cores but often also incorporates heterogeneous components such as GPUs or even FPGAs. During the last decade, a number of graph programming models (such as Google's Pregel) have been proposed but most of these focused defining high-level abstractions for distributed execution environments and introduced a significant runtime overhead. A potential approach for defining efficient graph processing algorithms is to exploit the well-known duality of graphs and sparse adjacency matrices, using matrix operations to capture algorithms. Surprisingly, only a few recent research prototypes have used this model with little consensus on the set of necessary building blocks. The GraphBLAS initiative (launched in 2013) aims to define a standard to capture graph algorithms in the language of linear algebra - following the footsteps of the BLAS standard which, starting four decades ago, revolutionized scientific computing by defining constructs on dense matrices. In this talk, I give an overview of the GraphBLAS standard and its key components. First, I illustrate how matrix operations on various semirings correspond to the steps in graph algorithms. I then use these operations to present fundamental graph algorithms such as breadth-first search, shortest paths, and the clustering coefficient. Finally, I demonstrate the scalability of the GraphBLAS-based algorithms with the LDBC Graphalytics benchmark. The presented implementations are available open-source as part of LAGraph, a library built on top of GraphBLAS to demonstrate how to design efficient algorithms in linear algebra. Intended audience: Developers interested in implementing high-performance graph algorithms. Expected prior knowledge: Familiarity with linear algebra helps plus but we only use basic concepts such as matrix-matrix multiplication

uk: вхід без авторизації

name: GraphBLAS: A linear algebraic approach for high-performance graph algorithms


uk: Комп'ютерні науки

description: The talk with give an introduction of Ansible collections and will talk about collection structure and how to deliver Ansible content with collections The agenda for this talk will be: 1) What are Ansible collections? 2) Why Ansible collections are required? 3) Deep dive with collections (init, create, build, publish) 4) Demo

uk: вхід без авторизації

name: Introduction to Ansible collections: Ansible collections, The future of Ansible content delivery


uk: Комп'ютерні науки

description: HOMER 2020: The future of the HEP Stack Meet the latest HOMER and its ground breaking features, and learn about our project vision for the future of HEP and OSS RTC monitoring tool and technologies

uk: вхід без авторизації

name: HOMER 2020: Meet the latest HOMER and its ground breaking features, and learn about our project vision for the future of HEP and RTC monitoring


AtomVM

uk: Комп'ютерні науки

description: This talk will present AtomVM, a tiny portable virtual machine that allows Elixir and Erlang code to run on microcontrollers with less than 500KB of RAM such as the ESP32 or several STM32. Erlang and Elixir are really good at handling network packets, running concurrent processes, dealing with faults, writing testable software and enabling rapid development. All this features are relevant for any language or framework that aims to IoT devices, therefore Erlang and Elixir might be good choice for IoT devices. However the BEAM, which is the standard Erlang and Elixir VM, cannot fit on those devices. AtomVM aims to overcome this limitation, by implementing a tiny virtual machine from scratch. This talk aims to present AtomVM and to show how a functional language such as Elixir might boost development of IoT projects.

uk: вхід без авторизації


de: Architektur, Innenarchitektur

uk: Архітектура, дизайн інтер'єру

en: Architecture, Interior Architecture

@language: de

uk: вхід без авторизації

name: Interventionen in ländlichen Räumen: Strukturalistische Analyse eines einfachen Hauses bei Brontallo im Tessin

name: Landluft - Verein zur Förderung von Baukultur in ländlichen Räumen


keywords: openaccess vernetzung openaccessnet

uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

en: Information and Library Sciences

de: Geisteswissenschaften

uk: Гуманітарні науки

en: Humanities

description: Der Vortrag stellt das Projekt open-access.network vor inkl. der Ziele, der Ausrichtung auf Wissenschaft und Multiplikator*innen, der geplanten Resultate und Möglichkeiten der Kooperation.

uk: вхід без авторизації

name: Kompetenzausbau und Vernetzung zu Open Access – Die bundesweite Plattform open-access.network

Technische Informationsbibliothek (TIB)

addressCountry: DE

addressLocality: Hanover

addressRegion: Lower Saxony

name: Berufsverband Information Bibliothek e. V. (BIB)


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: In large cultural heritage data aggregation systems such as Europeana, automatic and manual metadata enrichments are used to overcome the issues raised by multilingual and heterogeneous data. Enrichments are based on linked open datasets, which can be very beneficial for enabling retrieval across languages, adding context to cultural heritage objects and for improving the overall quality of the metadata. However, if not done correctly, the enrichments may transform into errors, which propagate to several languages and impacting the retrieval performance and user experience. To identify the different processes that impact the quality of enrichments, Europeana and affiliated projects’ representatives have organised a series of experiments applying several enrichment techniques on a particular dataset constituted of random metadata samples from several data providers from several domains, but mainly from library held cultural heritage digital objects. Comparing and analysing the results shows that selecting appropriate target vocabularies, fine-tuning enrichment rules are as important as defining evaluation methods. The development of flexible workflows will contribute to better interoperability between enrichment services and data, but might make individual enrichment processes more ambivalent. Efforts where users evaluate and correct enrichments as well as the enrichments’ impact on retrieval and user experience also need to be considered. The presentation will show how a better understanding of enrichment methodologies will help cultural heritage institutions and specifically libraries to get the semantics right.

uk: вхід без авторизації

name: Evaluation of Metadata Enrichment Practices in Digital Libraries: steps towards better data enrichments

name: ZBW – Leibniz-Informationszentrum Wirtschaft

addressLocality: Kiel

addressRegion: Schleswig-Holstein

name: Hochschulbibliothekszentrum des Landes Nordrhein-Westfalen (hbz)


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: The Linked Data for Libraries (LD4L) project aims to create a Linked Open Data (LOD) model that works both within individual institutions and across libraries to capture and leverage the intellectual value that librarians and other domain experts add to information resources when they describe, annotate, organize, and use those resources. First we developed a set of use cases illustrating the benefits of LOD in a library context. These served as a reference for the development of an LD4L ontology which includes bibliographic, person, curation, and usage information. This largely draws from existing ontologies, including the evolving BIBFRAME ontology. We have prioritized the ability to identify entities within library metadata records, reducing reliance on lexical forms of identity. Whenever possible we seek out persistent global identifiers for the entities being represented — identifiers from established efforts such as ORCID, VIAF, and ISNI for people, and OCLC identifiers for works for example. One group of LD4L use cases explores circulation and other usage data as sources that could improve discovery, and inform collection building. We are exploring the use of a anonymized and normalized metric that may be shared and compared across institutions. Ontology work and software from the LD4L project is available from our Github repository. SWIB15 Conference, 23 - 25 November 2015, Hamburg, Germany. http://swib.org/swib15 #swib15

uk: вхід без авторизації

name: Linked Data for Libraries: Experiments between Cornell, Harvard and Stanford


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: Pelagios is a community-driven initiative that facilitates better linkages between online resources documenting the past, based on the places they refer to. Our member projects are connected by a shared vision of a world in which the geography of the past is every bit as interconnected, interactive and interesting as the present. Pelagios has been working towards establishing conventions, best practices and tools in several areas of "Linked Ancient World Data": i. Linking and aligning of gazetteers. Gazetteers are the primary knowledge organization mechanism in Pelagios. In order to foster integration of gazetteers from different communities, we have been developing an RDF profile for publishing gazetteer metadata as Linked Open Data. ii. Tools to aid linking. To simplify the process of linking documents to the places they refer to, we have developed an Open Source geoannotation platform called Recogito. iii. Tools to visualize and navigate. To make the growing pool of data in Pelagios more accessible to everyday, we are working on a search engine called Peripleo. Peripleo will allow the navigation of the interconnected gazetteers that form the backbone of Pelagios, as well as the objects and documents that link to them. iv. Infrastructure for re-use. Data created in Recogito is available under CC terms for bulk download. Peripleo will feature similar capabilities and, in addition, offers a comprehensive JSON API to enable re-use in 3rd party applications and mashups. SWIB15 Conference, 23 – 25 November 2015, Hamburg, Germany. http://swib.org/swib15 #swib15

uk: вхід без авторизації

name: Linking Data about the Past through Geography: Pelagios, Recogito & Peripleo


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: It is often correctly noted that many datasets got published in the library world with little or no stories about actual use of these datasets. In this talk we want to highlight some of this usage in the context of the hbz linked open data service lobid (which stands for "linking open bibliographic data"). The hbz has been experimenting with linked data technology since 2009. In November 2013 the hbz launched a linked open data API via its service lobid. This API provides access to different kinds of data: • bibliographic data from the hbz union catalogue with 20 million records and 45 million holdings • authority data from the German Integrated Authority File (Gemeinsame Normdatei, GND) with subject headings, persons, corporate bodies, events, places and works • address data on libraries and related institutions, taken from the German ISIL registry and the MARC organization codes data base. The talk starts with a brief outline of the concept and the technology used behind the lobid API and how lobid itself benefits from other linked data sources. After that it is shown how applications are making use of the lobid API, focusing on the development of the North Rhine-Westphalian bibliography (NWBib) as an example. In the end we provide some lessons learned regarding the transformation of legacy data to linked data and the provision of a web API for it. SWIB15 Conference, 23 - 25 November 2015, Hamburg, Germany. http://swib.org/swib15 #swib15

uk: вхід без авторизації

name: LOD for Applications - Using the Lobid API


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: Linked Data (LD) and related technologies are providing the means to connect high volumes of disconnected data at Web-scale and producing a huge global knowledge graph. The key benefits of applying LD principles to datasets are i. better modelling of datasets as directed labelled graphs, ii. structural interoperability of heterogeneous resources, iii. federation of resources from different sources and at different layers inlcuding language annotation, iv. a strong ecosystem of tools based on RDF and SPARQL, v. improved conceptual interoperability due to strong semantic models such as OWL and shared semantics due to linking and vi. dynamic evolution of resources on the web. In this talk, I will explore challenges related with the (Re)Usability of library linked metadata in the field of cultural heritage and for other purposes. I will argue that for maximizing (re)use of library linked metadata it is crucial to represent core aspects related with Linguistic, Provenance, License, and Dataset metadata. A proper representation of these features using W3C standards and the use of W3C best practices and guidelinesfor multilingual Linked Open Data: i. produce better library linked metadata that could be used later on for diagnosing and repairing other external resources; ii. facilitate rights management, and consequently the access and reuse of metadata and data delivered under different license schema; iii. enable navigation across datasets in different languages thanks to the exploitation of links across multilingual data; iv. help data providers and data consumers to go a step further when cataloguing, searching and building cross-lingual applications that use open library linked metadata; v. increase exploitation when library linked metadata will be used with licensed (open or closed) linked data in other domains. I will also present approaches that use datos.bne.es library linked metadata with geographical information to produce new insights and innovation. SWIB15 Conference, 23 – 25 November 2015, Hamburg, Germany. http://swib.org/swib15 #swib15

uk: вхід без авторизації

name: Maximising (Re)Usability of Library Metadata Using Linked Data


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: Advocates for the use of RDF as a model for metadata in the cultural heritage sector have frequently spoken of the death of the “record”. Indeed, the shift from a document-centric approach to one based on identified resources and atomic statements is an important one. Yet current work on validation as well as requirements for day-to-day metadata management and attribution point back to aspects of a record-driven worldview. This session will address some historical views of records, contrasting them with the formal model adopted by RDF 1.1 and commonly accepted best practices for Linked Data. Practical implications of the RDF model will be explored, with questions raised regarding the management of state, mutability, and “record” workflows. A provisional approach for managing RDF resources and graphs in record-like contexts is proposed, with connections to RDF Shapes, DC Application Profiles, and Linked Data Platform. Use cases from the Digital Public Library of America will be presented as illustrative examples.

uk: вхід без авторизації

name: Metadata Records & RDF: Validation, Record Scope, State, and the Statement-centric Model


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: Cultural heritage institutions are looking at crowdsourcing as a new way and opportunity to improve the overall quality of their data and contribute to a better semantic description and link to the web of data. This is also the case for Europeana, as crowdsourcing under the form of annotations is envisioned and being worked on in several projects. As part of the Europeana Sounds project, we have identified the user stories and requirements that cover the following annotation scenarios: open and controlled tagging; enrichment of metadata; annotation of media resources; linking to other objects; moderation and general discussion. The first success on bringing annotations to Europeana is the integration of annotations to Europeana objects made on the HistoryPin.org platform covering both the tagging and object linking scenarios. The next step, will be to help data providers to support annotation at their side, for which we are working with the Pundit annotation tool. As a central point on all the efforts around annotations is an agreement on how these should be modelled in a uniform way for all these scenarios, as it is essential to bring such information to Europeana and in a way that can also be easily exploited and shared beyond our portal. For this, we are using the recent Web Annotation Data Model supported by the Open Annotation community as it is the most promising model at the moment. Due to its flexible design, we have made recommendations on how it should be applied for these scenarios and we are looking for discussion/feedback from the community in the hope that it will help cultural heritage institutions to better understand how annotations can be modelled.

uk: вхід без авторизації

name: Modeling and Exchanging Annotations for Europeana Projects


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: This project will explore how American University in Cairo (AUC) faculty members distributed their scholarly and creative works, and how their names are identified in author identifier systems and/or on the Web. The goal is to explore how best to present their data as linked data. The project will use the AUC faculty’s names listed in AUC Faculty Publications: 2012 Calendar Year. Their names will be used to search in author identifier systems to answer; 1. If they are registered on these sites, 2. if their names are consistent, or with variants and how the variants are handled, 3. what metadata are included, 4. sources of data, and 5. other relevant data. The systems to be checked, but not limited to, are 1. ORCID (Open Researcher & Contributor ID), 2. ResearcherID, 3. Scopus Author Identifier, 4. arXiv Author ID, 5. eRA Commons Username, 6. AuthorClaim, 7. OpenID, 8. ISNI, 9. Library of Congress Name Authority File (LCNAF), 10. Virtual International Authority File (VIAF), and 11. Google Scholar. The presentation will include the overview of these systems. The data analysis and discussion will shed light on: 1. how some author identifier systems fail to represent some faculty members; 2. how the linked data model, such as BIBFRAME, can be used to better represent them and to increase their visibility on the Web, and 3. the collaborative roles for librarians and faculty members to contribute data into these systems. 4. The presentation will conclude with the discussion on the faculty’s potential use of the data to demonstrate the impact of their scholarly and creative works.

uk: вхід без авторизації

name: Researchers' Identity Management in the 21st Century Networked World: A Pilot / Case Study of AUC Faculty Publications


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: Data citations are more common today, but more often than not the references to research data don't follow any formalism as do references to publications. The InFoLiS project makes those "hidden" references explicit using text mining techniques. They are made available for integration by software agents (e.g. for retrieval systems). In the second phase of the project we aim to build a flexible and long-term sustainable infrastructure to house the algorithms as well as APIs for embedding them into existing systems. The infrastructure's primary directive is to provide lightweight read/write access to the resources that define the InFoLiS data model (algorithms, metadata, patterns, publications, etc.). The InFoLiS data model is implemented as a JSON schema and provides full forward compatibility with RDF through JSON-LD using a JSON-to-RDF schema-ontology mapping, reusing established vocabularies whenever possible. We are neither using a triplestore nor an RDBMS, but a document database (MongoDB). This allows us to adhere to the Linked Data principles, while minimizing the complexity of mappings between different resource representations. Consequently, our web services are lightweight, making it easy to integrate InFoLiS data into information retrieval systems, publication management systems or reference management software. On the other hand, Linked Data agents expecting RDF can consume the API responses as triples; they can query the SPARQL endpoint or download a full RDF dump of the database. We will demonstrate a lightweight tool that uses the InFoLiS web services to augment the web browsing experience for data scientists and librarians.

uk: вхід без авторизації

name: A RESTful JSON-LD Architecture for Unraveling Hidden References to Research Data


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: ALIADA is an open source solution designed by art libraries and museums, ILS vendors and experts on Semantic Web to help cultural heritage institutions to automatically convert, link and publish their library and museum data as Linked Open Data. If they can export their metadata as MARCXML or LIDOXML, they can choose ALIADA as their ally in the challenge of liberating cultural institutions from their current data silos and integrating library and museum data onto the Semantic Web. ALIADA uses its own ontology based on FRBRoo, SKOS, FoaF and WGS84, the ontologies most used by the linked open datasets analyzed during the design of the tool. It's expected this ontology to be updated with the new emerging models and vocabularies, such as RDA or BIBFRAME, according to the ALIADA's community demand. ALIADA can be integrated with the current management system in a library or a museum allowing non-expert staff to easily select and import metadata into ALIADA. Once the file is validated, the user can start the "RDFizer" to create the triples using the existing mapping templates. All the MARC mappings were not carried out into RDF using FRBRoo ontology because of the complexity of the format. Along with the RDF conversion, ALIADA provides a set of predefined SPARQL queries to check the URIs. The next step in the workflow is the linking to other datasets. ALIADA offers a list of external datasets that can be linked to, including Europeana, DBpedia or VIAF. Finally, ALIADA will show the dataset before publishing it on the DataHub.

uk: вхід без авторизації

name: ALIADA, an Open Source Solution to Easily Publish Linked Data of Libraries and Museums


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: This work describes how XML-based TEI documents, containing statistical data, can be normalized, converted and enriched using the RDF Data Cube Vocabulary. In particular we focus on a statistical real world data set, namely the statistics of the German Reich around the year 1880, which are available in the TEI format. The data is embedded in complex structured tables, which are relatively easy to understand for humans but they are not suitable for automated processing and data analysis, without heavy pre-processing, due to their varying structural properties and differing table layouts. Therefore, the complex structured tables must be validated, modified and transformed, until they are suitable for the standardized multi-dimensional data structure - the data cube. This work especially focuses on the transformations necessary to normalize the structure of the tables. Performing validation- and cleaning-steps, resolving row- and column-spans and reordering slices are available transformations among multiple others. By combining existing transformations, compound operators are implemented, which can handle specific and complex problems. The identification of structural similarities or properties can be used to automatically suggest sequences of transformations. A second focus is on the advantages, which come by using the RDF Data Cube Vocabulary. Also, a research prototype was implemented to execute the workflow and convert the statistical data into data cubes.

uk: вхід без авторизації

name: Data-Transformation on Historical Data Using the RDF Data Cube Vocabulary


keywords: trendmanagement bibstories

uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: Bibliotheken müssen technische Trends verstehen, um diese bewerten und in neue Dienstleistungen umsetzen zu können. Vorgehensweise, Aufwand und notwendige Ressourcen werden vorgestellt.

uk: вхід без авторизації

name: Hot Topics für New Professionals – Trendmanagement in Bibliotheken


keywords:
sommerkurs20
miteinander reden
partizipation

de: Sozialwissenschaften/Soziologie

uk: Суспільні науки та соціологія

en: Social Sciences/Sociology

uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

de: Rechts-, Wirtschafts- und Sozialwissenschaften

uk: Право, економіка та суспільні науки

en: Law, Economics and Social Sciences

uk: Гуманітарні науки

description: Der @bib_info sommerkurs20 wird virtuell. Wie – das wollen wir mit Ihnen weiterdenken. Das Thema steht, es geht um demokratiekompetenz, miteinander_reden und partizipation. Und um virtuelles Lernen…

uk: вхід без авторизації

name: Miteinander reden. Demokratiekompetenz virtuell vermitteln


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

uk: вхід без авторизації

name: Wir gestalten Wissensräume: Strategie-Entwicklung an der Freie Universität Berlin


openBnBib

keywords: openBnBib openbiblojobs LIS_Community

uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

de: Geowissenschaften (ohne Geographie)

uk: Науки про Землю(крім географії)

en: Geosciences (excl. Geography)

de: Mathematik, Naturwissenschaften

uk: Математика, природничі науки

en: Mathematics, Natural Sciences

uk: Гуманітарні науки

description: openBnBib Angedockt an das bewährte openbiblio openbiblojobs Modell sollen für (fachliche) Aufenthalte in der #LIS_Community Übernachtungsmöglichkeiten angeboten werden

uk: вхід без авторизації

name: Berufsverband Information Bibliothek e. V. (BIB)


keywords: agiles-projektmanagement scrum agile

uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: Agile-Management-Tools erleichtern das agile Projektmanagement und machen es effizienter. Der Vortrag definiert allgemeine Anforderungen an ein Agile-Management-Tool, also das, was ein Agile-Management-Tool können muss

uk: вхід без авторизації

name: Softwaregestütztes agiles Projektmanagement – Was muss ein Agile-Management-Tool können?


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: "The IIIF Presentation API specifies a web service that returns JSON-LD structured documents that together describe the structure and layout of a digitized object or other collection of images and related content." IIIF website The dynamic serialization of IIIF JSON-LD structured manifests via SPARQL CONSTRUCT is an interesting possibility that has great potential for cross-domain discovery and rendering of digitized objects with variable criteria. I have explored this possibility by implementing a data model in the Fedora Commons Repository that matches the specifications of the IIIF Presentation API. Fedora has the facility to index objects via Apache Camel directly to a triplestore. With SPARQL CONSTRUCT, the triplestore can serialize normalized JSON-LD as a graph. The use of "ordered lists" (aka collections) is a fundamental component of JSON-LD and necessary feature of the IIIF manifest sequence which is represented in a canonical RDF graph as a cascade of blank nodes. In order to dynamically create the sequence with SPARQL requires that the data is modelled identically to the IIIF specification. This gist is a representation of a compacted and framed JSON-LD graph that was serialized from a SPARQL query of Fedora metadata. The ability to assemble parts of distinct, disparate and disassociated digital objects on demand in one cohesive presentation becomes a real possibility. For example, the "range" object is equivalent to a part of a sequence, like a chapter in a book. With SPARQL, it is possible to target ranges from different "editions" based on a metadata specification (i.e. a person, place, or date) and unify them in a manifest object which is then rendered by a client viewer like OpenSeadragon.

uk: вхід без авторизації

name: Implementing the IIIF Presentation 2 0 API as a Linked Open Data Model in the Fedora Repository

name: ZBW – Leibniz-Informationszentrum Wirtschaft


Improving data quality at Europeana

uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: Europeana aggregates metadata from a wide variety of institutions, a significant proportion of which is of inconsistent or low quality. This low-quality metadata acts as a limiting factor for functionality, affecting e.g. information retrieval and usability. Europeana is accordingly implementing a user- and functionality-based framework for assessing and improving metadata quality. Currently, the metadata is being validated (against the EDM XML schema) prior to being loaded into the Europeana database. However, some technical choices with regard to the expressions of rules impose limitations on the constraints that can be checked. Furthermore, Europeana and its partners sense that more than simple validation is needed. Finer-grained indicators for the 'fitness for use' of metadata would be useful for Europeana and its data providers to detect and solve potential shortcomings in the data. Beginning 2016, Europeana created a Data Quality Committee to work on data quality issues and to propose recommendations for its data providers, seeking to employ new technology and innovate metadata-related processes. This presentation will describe more specifically the activities of the Committee with respect to data quality checks: - Definition of new data quality requirements and measurements, such as metadata completeness measures; - Assessment of (new) technologies for data validation and quantification, such as SHACL for defining data patterns; - Recommendations to data providers, and integration of the results into the Europeana data aggregation workflow.

uk: вхід без авторизації

name: Hochschulbibliothekszentrum des Landes Nordrhein-Westfalen (hbz)


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: The publication of EPUB3 has been a major step forward digital publishing. Relying on Web Technologies like HTML, CSS, SVG, and others, EPUB3 offers a solid basis to publish not only digital books, but all sorts of digital publications in a portable, adaptable and accessible manner. However, it is possible to bring the publishing and the Web world even closer together, making the current format- and workflow-level separation between offline/portable and online (Web) document publishing eventually disappear. These should be merely two dynamic manifestations of the same publication: content authored with online use as the primary mode can easily be saved by the user for offline reading in portable document form. Content authored primarily for use as a portable document can be put online, without any need for refactoring the content. Essential features flow seamlessly between online and offline modes; examples include cross-references, user annotations, access to online databases, as well as licensing and rights management. W3C and IDPF have recently started to work towards this vision, exploring the technical challenges to make it a reality; this talk will give an overview on where we are.

uk: вхід без авторизації

name: Welcome and Keynote: (Packaged) Web Publication


Linked Data for Production

uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: The Mellon Foundation recently approved a grant to Stanford University for a project called Linked Data for Production (LD4P). LD4P is a collaboration between six institutions (Columbia, Cornell, Harvard, Library of Congress, Princeton, and Stanford University) to begin the transition of technical services production workflows to ones based in Linked Open Data (LOD). This first phase of the transition focuses on the development of the ability to produce metadata as LOD communally, the enhancement of the BIBFRAME ontology to encompass multiple resource formats, and the engagement of the broader academic library community to ensure a sustainable and extensible environment. As its name implies, LD4P is focused on the immediate needs of metadata production such as ontology coverage and workflow transition. In parallel, Cornell also has been awarded a grant from the Mellon Foundation for Linked Data for Libraries-Labs (LD4L-Labs). LD4L-Labs will in turn focus on solutions that can be implemented in production at research libraries within the next three to five years. Their efforts will focus on the enhancement of linked data creation and editing tools, exploration of linked data relationships and analysis of the graph to directly improve discovery, BIBFRAME ontology development and piloting efforts in URI persistence, and metadata conversion tool development needed by LD4P and the broader library community. The presentation will focus on a brief description of the projects, how they interrelate, and what has been accomplished to date. Special emphasis will be given to extensibility and interactions with the broader LOD community.

uk: вхід без авторизації


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: Emblematica Online allows humanities scholars to seamlessly discover and link to items in a unique virtual emblem corpus distributed across six institutions in the US and Europe. The site supports multi-granular discovery of 1,400+ digitized emblem books and 25,000+ individual emblems from selective emblem books. To better integrate with related digital images and textual resources elsewhere, and to provide additional context for users, the site exploits linked open data (LOD) in two ways. First, as a producer of LOD, it publishes emblem and emblem book metadata as HTML+RDFa with schema.org semantics, making emblem resources more visible and useful in a linked open data context. Second, as a consumer of LOD, it enhances user experiences by utilizing LOD services and resources. For example, using the Iconclass LOD service, Emblematica Online supports multi-lingual browsing of the Iconclass vocabulary and connects users to digital sources elsewhere that share Iconclass descriptors. Also, it provides additional context about authors and contributors, including gender, nationality, and occupation, by reconciling names appearing in emblem metadata with LOD sources, such as the VIAF, DNB, and Wikipedia. This presentation discusses how Emblematica Online publishes its metadata as LOD and improves user experience using LOD sources as well as Emblem ontology development and plans for new services that allow possible reuse of Emblem LOD.

uk: вхід без авторизації

name: Linked Open Data in Practice: Emblematica Online


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: Imagine a theatre play. There are contributors such as the playwright, director, actors, etc. The play may have several performances with changing casts while actors may contribute to other plays. The play might be based on a drama which also has a screen adaption. All this is documented in manuscripts, photos, videos and other materials. The more relations you find among these performance-related objects, the more it emerges as a perfect use case for linked data. At the University Library Frankfurt am Main, the Specialised Information Service Performing Arts aggregates performing arts-related metadata of artefacts gathered by German-speaking cultural heritage institutions. It is funded by the German Research Foundation and aims to give researchers access to specialized information by providing a VuFind-based search portal that presents the metadata modeled as linked and open data. The Europeana Data Model (EDM) offers a universal and flexible metadata standard that is able to model the heterogeneous data about cultural heritage objects resulting from the data providers’ variety of data acquisition workflows. Being a common aggregation standard in digitization projects a comprehensive collection of mappings already exists. With the amount of delivered manuscript data in mind, the DM2E-extension of EDM was used and further extended by the ECLAP-namespace covering the specific properties for the performing arts domain. The presentation will show real life examples and focus on the modeling as linked data and the implementation within the VuFind framework.

uk: вхід без авторизації

name: Performing LOD: Using Europeana Data Model for the aggregation of metadata from the performing arts domain


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: Continuing the longstanding research program by OCLC in the field of linked data, recent projects have focused on creating sets of entities of high interest for any organization wanting to utilize linked data paradigms. Through intensive mining and clustering of WorldCat bibliographic data, name and subject authority files, and other related data sets, OCLC has produced over 300 million entity representations. These clusters pull together and represent creative works, and persons related to those works. OCLC has engaged with a number of libraries and organizations to create and experiment with this data. A pilot project during October 2015-February 2016 to explore new methods of providing access to Person entities provided a number of new directions and insights. The core purpose of the work is to understand how these entities might best be leveraged to make library workflows more efficient, and to improve the quality of metadata produced in the library sector. This presentation will provide a background on data used in the project, as well as the development of services and APIs to provision the data. It will address challenges and opportunities in the area of creating and managing entities, and ways in which they could be improved and enriched over time.

uk: вхід без авторизації

name: Person Entities: Lessons learned by a data provider


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: RDF is a graph data model, so the best way to understand RDF data schemas (ontologies, application profiles, RDF shapes) is with a diagram. Many RDF visualization tools exist, but they either focus on large graphs (where the details are not easily visible), or the visualization results are not satisfactory, or manual tweaking of the diagrams is required. We describe a tool *rdfpuml* that makes true diagrams directly from Turtle examples using PlantUML and GraphViz. Diagram readability is of prime concern, and rdfpuml introduces various diagram control mechanisms using triples in the puml: namespace. Special attention is paid to inlining and visualizing various Reification mechanisms (described with PRV). We give examples from Getty CONA, Getty Museum, AAC (mappings of museum data to CIDOC CRM), Multisensor (NIF and FrameNet), EHRI (Holocaust Research into Jewish social networks), Duraspace (Portland Common Data Model for holding metadata in institutional repositories), Video annotation. If the example instances include SQL queries and embedded field names, they can describe a mapping precisely. Another tool *rdf2rdb* generates R2RML transformations from such examples, saving about 15x in complexity.

uk: вхід без авторизації

name: RDF by Example: rdfpuml for True RDF Diagrams, rdf2rml for R2RML Generation


Swissbib Goes Linked Data

uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: The project linked.swissbib.ch aims to integrate the Swiss library metadata into the semantic web. A Linked Data infrastructure has been created to provide on the one hand a data service for other applications and on the other hand an improved interface for the end user (e.g. a searcher). The workflow for the development of this infrastructure involves basically five steps: (1) data modeling and transformation in RDF, (2) data indexing, (3) data interlinking and enrichment, (4) creation of a user interface and (5) creation of a RESTful API. The project team would like to highlight some challenges faced during these stages, and the means found to solve them. This includes for example the conception of various use cases of innovative semantic search functionalities to give specifications for data modelling, data enrichment and for the design of the search index. Data processing operations such as transformation and interlinking must be highly scalable, with the aim of an integration in the workflow of the already existing system. Wireframes have been made to realize early usability evaluations. Finally, negotiations have been undertaken with the various Swiss library networks to adopt a common open license for bibliographic data.

uk: вхід без авторизації


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: One of the key goals of Cornell University Library (CUL) is to ensure preservation of the scholarly works being published by the Cornell faculty members and other researchers. VIVO is an open source and semantic technologies driven application that enables the preservation and open access of the scholarship across institutions. Driven by different needs, users look at VIVO implementation at Cornell from different viewpoints. The college requires the structure data for reporting needs. The library is interested in preservation of the scholarship data. University executives are interested in identifying the areas where they should invest in the forthcoming future. First, these viewpoints do not completely overlap with each. Second, current user interface represents the scholarship data in the list view format. Such representation of the scholarship data is not easy to use and consumable by the users. In this presentation, we present our ongoing work of integration of D3 visualizations into the VIVO pages. Such visualizations are constructed on the fly based on the underlying RDF data. A visualization-driven approach provides an efficient overview of the huge linked data network of interconnected resources. These visualizations are intuitive for the users to interact and offer the ability to visualize and navigate through the large linked data network. We discuss the performed (data) gap analysis as well as a few of the visualizations in detail and their integration into the VIVO framework.

uk: вхід без авторизації

name: Towards visualizations-driven navigation of the scholarship data


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: During the second World War some 1.300 illegal newspapers were issued by the Dutch resistance. Right after the war as many of these newspapers as possible were physically preserved by Dutch memory institutions. They were described in formal library catalogues that were digitized and brought online in the ‘90s. In 2010 the national collection of underground newspapers – some 200.000 pages – was full-text digitized in Delpher, the national aggregator for historical full-texts. Having created online metadata and full-texts for these publications, the third pillar ''context'' was still missing, making it hard for people to understand the historic background of the newspapers. We are currently running a project to tackle this contextual problem. We started by extracting contextual entries from a hard-copy standard work on Dutch illegal press and combined these with data from the library catalogue and Delpher into a central LOD triple store. We then created links between historically related newspapers and used Named Entity Recognition to find persons, organisations and places related to the newspapers. We further semantically enriched the data using DBPedia. Next, using an article template to ensure uniformity and consistency, we generated 1.300 Wikipedia article stubs from the database. Finally, we sought collaboration with the Dutch Wikipedia volunteer community to extend these stubs into full encyclopedic articles. In this way we can give every newspaper its own Wikipedia article, making these WW2 materials much more visible to the Dutch public, over 80% of whom uses Wikipedia. At the same time the triple store can serve as a source for alternative applications, like data visualizations. This will enable us to visualize connections and networks between underground newspapers, as they developed over time between 1940 and 1945. SWIB16 Conference, 28 - 30 November 2016, Bonn, Germany http://swib.org/swib16/ #swib16 Licence: CC-BY-SA https://creativecommons.org/licenses/by-sa/3.0/

uk: вхід без авторизації

name: Using LOD to crowdsource Dutch WW2 underground newspapers on Wikipedia


Who is using our linked data?

uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: The British Library published the first Linked Open Data iteration of the British National Bibliography (BNB) in 2011. Since then it has continued to evolve with regular monthly updates, addition of new content (e.g. serials) and new links to external resources (e.g. International Standard Name Identifier (ISNI)). Data is available via deferenceable URIs, a SPARQL endpoint and RDF dataset dumps. There has been clear value to the Library in its linked data work, e.g. learning about RDF modelling and linked data. However, like many linked open data publishers, the Library has found it challenging to find out how the data has been used and by whom. Although basic usage data are captured in logs, there is currently no widely available tool to extract Linked Open Data insights. This makes it challenging to justify continued investment at a time of limited resourcing. This talk will report on collaboration between Fujitsu Laboratories Limited, Fujitsu Ireland and the British Library in the development of a Linked Open Data Analytics platform. The aim of the project was twofold: to examine Linked Open BNB usage and to potentially develop a tool of interest to the wider Linked Open Data community. We will describe the analytics platform and the functionality it provides as well as demonstrate what we found out about the usage of our data. Over the period under consideration (April 2014-April 2015) usage of the Linked Open BNB increased, and there was a discernible growth in the number of SPARQL queries relative to HTTP queries. Usage patterns were traced to the addition of new metadata elements or to linked data tuition sites or events.

uk: вхід без авторизації


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: In the past years, the number of references to places, peoples, concepts and time in Europeana’s metadata has grown considerably and with it new challenges have arisen. These contextual entities are provided as references as part of the metadata delivered to Europeana or selected by Europeana for semantic enrichment or crowdsourcing. However their diversity in terms of semantic and multilingual coverage and their very variable quality make it difficult for Europeana to fully exploit this rich information. Pursuing its efforts towards the creation of a semantic network around cultural heritage objects and intending in this way to further enhance its data and retrieval across languages, Europeana is now working on a long term strategy for entities. The cornerstone of this strategy is a “semantic entity collection” that acts as a centralised point of reference and access to data about contextual entities, which is based on the cached and curated data from the wider Linked Open Data cloud. While Europeana will have to address the technical challenges of integration and representation of the various sources, it will also have to define a content and curation plan for its maintenance. This presentation will highlight the design principles of the Europeana Entity Collection and its challenges. We will detail our plans regarding its curation and maintenance while providing the first examples of its use in Europeana users' services. We will also reflect on how our goals can fit our partners' processes and how can organizations like national cultural heritage portals and smaller institutions contribute to (and benefit from) such a project as a network.

uk: вхід без авторизації

name: Entitifying Europeana: building an ecosystem of networked references for cultural objects


From MARC silos to Linked Data silos?

uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: Many libraries are experimenting with publishing their metadata as Linked Data in order to open up bibliographic silos, usually based on MARC records, and make them more interoperable, accessible and understandable to developers who are not intimately familiar with library data. The libraries who have published Linked Data have all used different data models for structuring their bibliographic data. Some are using a FRBR-based model where Works, Expressions and Manifestations are represented separately. Others have chosen basic Dublin Core, dumbing down their data into a lowest common denominator format. The proliferation of data models limits the reusability of bibliographic data. In effect, libraries have moved from MARC silos to Linked Data silos of incompatible data models. Data sets can be difficult to combine, for example when one data set is modelled around Works while another mixes Work-level metadata such as author and subject with Manifestation-level metadata such as publisher and physical form. Small modelling differences may be overcome by schema mappings, but it is not clear that interoperability has improved overall. We present a survey of published bibliographic Linked Data, the data models proposed for representing bibliographic data as RDF, and tools used for conversion from MARC. We also present efforts at the National Library of Finland to open up metadata, including the national bibliography Fennica, the national discography Viola and the article database Arto, as Linked Data while trying to learn from the examples of others.

uk: вхід без авторизації


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: Recording information about countries, conferences, organizations and concepts in a Linked Data application like VIVO means at the first stage an initial import of a large number of data items, which beforehand must be transformed into RDF and manually enriched with persistent identifiers, geographic position, short description, and multilingual labels. Collecting, enriching and converting such an amount of information cost considerable temporal and administrative efforts. Storage of the amount of data can slow down the performance, responsiveness and reasoning processes of an application. Lookup services, already developed for VIVO, DSpace-CRIS, Linked Data for Libraries (LD4L) and other projects are aimed to facilitate the integration of external authority data. Whereas some vocabularies and data sources like EuroVoc and Wikidata offer a SPARQL endpoint, other authority data sources such as the Integrated Authority File of the German National Library (GND) provide only data dumps. Our objective is to enable a combined access to external sources via a single interface, using Named Entity Recognition tools, APIs and SKOSMOS in the background. Beside concepts we would also provide integration of such data items as events, organizations and languages, supplemented with additional information, which requires mappings between source and target systems in order to insert and display attributes and relations of the selected entities. Furthermore we investigate the automated transferring of the changes made in external vocabularies to the data in the target system. This presentation outlines our achievements and lessons learned concerning the integration of semantically structured and enriched data from distributed sources via lookup services, similar to the external vocabulary services in VIVO and related projects.

uk: вхід без авторизації

name: Integrating Distributed Data Sources in VIVO via Lookup Services


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: Scientific names are important access points to biodiversity literature and significant indicators of content coverage. The Biodiversity Heritage Library (BHL) mines its content using the open source Global Names Recognition and Discovery (GNRD) tool from the Global Names Architecture (GNA) suite of machine learning and named entity recognition algorithms, to extract scientific names to index and attach to page records. The 2017 BHL National Digital Stewardship Residents (NDSR) are working collaboratively on a group of projects designed to deliver a set of best practices recommendations for the next version of the BHL digital library portal. NDSR Residents Katie Mika and Alicia Esquivel will discuss (i.) BHL and the significance of taxon names, (ii.) the current workflow, proposed improvements, and example workflows for linking content across scientific names including semantic linking to biodiversity aggregators such as Encyclopedia of Life and the Global Biodiversity Information Facility, (iii.) how to use scientific names for content analysis, and (iv.) optimizing manuscript transcription of archival content, which introduces problems like outdated and common names, misspellings, and antiquated taxonomies to GNA tools. Authors invite questions, comments, and discussion from audience members as the Residents prepare to submit their final recommendations at the end of the year.

uk: вхід без авторизації

name: Improving Named Entity Recognition in the Biodiversity Heritage Library with Machine Learning


High Quality Linked Data Generation

uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: Linked Data allows the description of domain-level knowledge that is understandable by both humans and machines. Nevertheless, as machines are intolerant of unexpected input, the quality of the underlying Linked Data largely determines the success of the envisaged Semantic Web. Despite, though, the significant number of existing tools, generating Linked Data by incorporating heterogeneous data from multiple sources and different formats into the Linked Open Data cloud remained complicated, let alone generating their metadata. Raw data values are expected to be used as extracted, while when data transformations occur, they remain coupled and case-specific in separate not-reusable systems. Moreover, quality assessment is performed after Linked Data is published and adjustments are manually – but rarely – applied, while the violations root is not identified. In this talk, we present a sustainable semantic-driven approach, based on the RML toolchain (RML Mapper, RML Workbench, RML Editor and RML Validator), which we adopt to address the aforementioned shortcomings and enables data owners to generate high quality Linked Data by themselves. This way, we facilitate and automate the generation of high quality Linked Data with accurate, consistent and complete metadata, offering a granular, sustainable and generic solution that shortens the Linked Data generation workflow, and achieves higher integrity within Linked Data.

uk: вхід без авторизації


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: The Dutch Digital Heritage Network (NDE) started in 2015 by the national cultural heritage institutions as a joint effort to improve the visibility, usability and sustainability of the cultural heritage collections maintained in the GLAM institutions. One of the goals is the realization of a distributed network of heritage information that no longer depends on aggregation of the data. This talk will focus on our approach for developing a new, cross-domain, decentralized discovery infrastructure for the Dutch heritage collections. A core element in our strategy is to encourage institutions to align their information with formal Linked Data resources for people, place, periods, concepts and to publish their data as Linked Open Data. The NDE program works on making all relevant terminology sources available as Linked Data and provide facilities for term alignment and building new thesauri. Another important goal is to provide means for browsing the collections in a cross-domain, user centric fashion. Based on possible relevant URIs identified in the user queries we want to be able to browse the available Linked Data in the cultural heritage network. The bi-directional use of Linked Data without aggregation is still a technological challenge. We decided to build a registry that records the back links for all the URIs used in our network. Next to Linked Data definitions of organizations and datasets we will also record fingerprints of the object descriptions. This information will provide the back links which make it possible to navigate from a term URI to the objects that have a relation with this term. We are currently developing a Proof-of-Concept and will show the first results at the SWIB conference.

uk: вхід без авторизації

name: A distributed Network of Heritage Information


uk: Комп'ютерні науки

uk: Бібліотекознавство, документознавство

uk: Гуманітарні науки

description: The University of Alberta is actively trying to ramp up for Linked Data through local experimentation, research and partnerships with other institutions. Though BIBFRAME is still in development, several transformation tools have already been created, and with many libraries thinking about planning for moving to Linked Data it would seem timely to compare approaches to moving legacy MARC data to BIBFRAME. Setting aside the question of whether BIBFRAME should be the approach for libraries to move to Linked Data, this investigation aimed at comparing two tools for converting MARC to bf:2.0: A) LC MARC to BIBFRAME XSLT: An XSLT 1.0 application aimed at converting MARC to RDF/XML released in March 2017; and B) Casalini SHARE Virtual Discovery Environment: A project by Casalini Libri and @Cult to develop a Linked Data discovery environment, including a conversion tool for MARC to bf:2.0 RDF. Through the comparison and analysis of these transformation tools several topics will be explored: Comparison of underlying development models and performance of the tools; Comparison of data element conversion and impact for discovery; Impact of content standard on conversion efficacy (AACR vs. RDA); Implications for conversions for various formats (monographs, serials, et cetera); URI enrichment pre/post conversion; In house and vendor workflow implications.

uk: вхід без авторизації

name: Will you be my bf: forever? Analysing Techniques for Conversion to BIBFRAME