Sign up for an account to create a profile with publication list, tag and review your related work, and share bibliographies with your co-authors. Sign in or sign up to see more results. In Collection. In Proceedings. Journal Article. XML Schema. Alice Tani. Costantino Perciante. Costantino Thanos. Donatella Castelli.
Fabio Sinibaldi. Francesco Mangiacrapa. Giancarlo Panichi. Gianpaolo Coro. Giuseppe Amato. Heiko Schuldt. Leonardo Candela. Edited Volume - Contentious Migrant Solidarity.
Monograph - Migrant Protest. Journal Article - We protect the forest beings, and the forest beings protect us: Cultural resistance in the Ecuadorian Amazonia Leonidas Oikonomakis. In a D-NET infrastructure, by exploiting sharing, distribution, compositionality, autonomicity orchestration and customizability of services, multiple organizations can collaboratively construct their ADLSs in a sustainable way. Specifically, one responsible organization RO administrates the infrastructure and supports a number of participating organizations POs at realizing and maintaining their ADLSs.
The Data and User Functionality Areas include the services shown in Figure 2 below, used to form aggregation systems and portals respectively. Services in both areas are designed to be generic with respect to the metadata format they can manage, so that they can be instantiated to match the requirements of their communities. In particular, the Generic UI Service can be configured, personalized and instantiated in an infrastructure to set up a portal.
Such portals can integrate none or some of the user functionalities available through the running services. In D-NET ADLSs are constructed by following a "Lego" approach, that is, by deploying services of data and functionality areas and combining them into workflows, based on their application requirements.
For example Figure 3 , an aggregation system is a D-NET application [ 22 ] consisting of data areas services running in possibly multiple instances, so as to handle record replicas or record distribution vertical and horizontal partitioning at different sites. Services can be combined through customized workflows, in order to match the requirements of different aggregation systems; e.
Similarly, portals consist of a number of Functionality Area services see Figure 4. Appropriately combined, such services can form a variety of community portals, which can be configured to operate over one of the available information spaces.
In particular, portals are modularly independent from the aggregation systems and can automatically adapt to any metadata format supported by the relative information spaces; moreover, they can be configured to focus on a subpart of one information space and to activate only the subset of functionalities of interest. Most importantly, D-NET's framework is "open", i.
In the following, we shall describe the cost model entailed by the D-NET framework and report on real-world scenarios. This analysis will show that, compared to the traditional approach, adopting D-NET generally implies minor realization costs to the organizations and results in production systems that are more sustainable in the long-term.
Table 2 reflects this distinction by introducing the role of RO administrators. It can be observed that while librarians and aggregator managers perform the same work as they would for traditional ADLSs, all other actors are either freed or facilitated in their tasks by the framework and orchestration mechanisms and software realization and maintenance costs are eliminated or softened.
Costs for ROs. ROs bear the costs of administrators installing and maintaining the infrastructure and all PO applications. Infrastructure installation and maintenance.
Infrastructure administration. Experience has proven that such costs are similar to that of installing and maintaining traditional ADLSs. In fact, the cost of monitoring the higher number of ADLSs that can be hosted in a D-NET environment is compensated by Manager Service orchestration mechanisms monitoring availability, performance, workload, etc.
Autonomic administration, normally missing in traditional ADLS technologies, frees administrators of monitoring and management tasks, and warns them in the case of major failures. Costs for Pos. In particular, given the current D-NET service packages, POs can exploit two main application patterns: aggregation system and portal applications. Services in the Data and Functionality Areas can be combined, orchestrated and configured adapted to a given metadata format by the PO or the RO to satisfy the given PO's application scenario, i.
Realization costs are therefore minimal for the PO involved, which need only deploy the services and supply the appropriate customized portal graphics. The extent of sharing is decided and evaluated by the POs involved and the RO. In some cases, PO applications may fully dependent on other POs machines, with zero hardware costs.
ADLS administrators are not required, to a large extent, since RO administrators can configure the Manager Services to orchestrate services to satisfy requirements of robustness and scalability, i. When needed, new services can be deployed any time to dynamically empower the infrastructure with new resources.
Costs for librarians and aggregation managers are the same as for traditional ADLSs. Aggregator Managers can rely on push-button interfaces, through which they can define format-to-format mappings without specific programming skills. XSLT defined mappings are still possible. A further level of participation is that of POs willing to include new typologies of services into D-NET or provide better implementations of existing typologies.
Design and development cost are necessary, however D-NET's openness eases the integration of the new services. Two aspects further reduce refinement costs: 1 any D-NET enhancement can be reused by other PO applications and 2 D-NET services can naturally adapt to changes by simple configuration, e.
Its flexible software can be installed and configured to match the ADLS requirements of the organization involved. Administration costs, as described above, are equivalent. A further benefit is that the resulting production system can be flexibly extended with further functionality or dynamically adapted to change its behavior, e.
Maintenance costs are therefore minor with respect to ad-hoc technological solutions. Such resources can be movies, persons, corporate bodies, posters, audio-video material, all generally described by heterogeneous metadata formats at the original sites.
The EFG Consortium has defined a common EFG metadata format, onto which the metadata records from the data providers must be mapped, and has provided the specification of the portal through which such data will have to be searched and accessed. D-NET was convenient for two main reasons: the possibility of configuring an aggregation system to handle the EFG information space; and the openness and flexibility of the resulting production system. Realization costs were the installation of a D-NET infrastructure, the configuration and deployment of the aggregation system and portal, for an initial cost of one day of work and three servers in a local network.
Aggregator Managers costs for defining format-to-format mappings are limited to the 15 data sources and therefore limited to an initial effort. Librarian costs remain as they would in the OAIster or any other system.
Two further POs, i. Today, the DIS counts around 2,, metadata records for open access publications, harvested from more than open access repositories from 33 countries in Europe and beyond. The number of entries is expected to keep growing as repository organizations are attracted to become data provider to increment their visibility, thus recompensing their local efforts, and to get feedback on the quality of their service through special D-NET Validator Services, capable of ranking quality of repository content.
DMF records describe publication resources in terms of their provenance name of the aggregator that fetched them, of the original repository, of the institution and country and Dublin Core [ 21 ] bibliographical description. They are generated by a set of Transformation Services, whose aggregator managers apply cleaning and mapping rules to the DC records harvested from repositories. Note that the responsibility of such services can be delegated to national organizations so as to distribute the overall aggregative effort.
As of , Slovenia and Spain are examples of this methodology, while Belgium, Greece and Bulgaria are on the waiting list for technical support. Manager Services, given the mapping from DC to DMF for a given repository, are configured to orchestrate the workflow maintaining the DIS, which is: harvesting DC records, storing and transforming them onto DMF records, indexing DMF records, and maintaining three replicas of all stores and indices on different servers this number can be varied any time.
0コメント