Thread. All sewing threads to be color fast polyester wrap to match. INTERLININGS: Collar shall be interlined with #285 Stabilized MelloPress. Cuffs, pocket flaps, shoulder straps and top center to be interlined with #550 Stabilized MelloPress. Collar band interlining to be Crease-N-Tack.
Thread. Section 3.3.3
Thread. All thread shall be polyester wrapped on monofilament polyester. Color to match.
Thread fork fork’ Thread.thread → fork’ (fun () startServer (recv c)) :
Thread. 2 – OIS implementation (M4-M8, CNR) The result of this thread will result in one of the cornerstone components of the OpenAIRE system, as it will support the implementation of all scenarios depicted above. In particular, based on the data model resulting at Month 4, CNR will modify D-NET to host project information, article information and their relationships in a traditional database framework. To this aim a new D-NET service, called the DB Service will be designed and developed to host a relational database (Postgres) capable of serving SQL clients (posing DDL, DML and DQL requests) and capable of synchronizing with the D-NET Information Service (IS). The reason for storing OIS entities in a relational database and in the IS is twofold: on the one hand we want to provide fast and efficient responses to queries used in document-project related statistics;; on the other hand, the same OIS entities will be also treated as D-NET system resources in the Information Service, so that D-NET services are able to interact with them (e.g., subscribe to their actions) in the infrastructure eco-system. An example is a repository, whose information will be in the OIS to be used in statistics calculations, and perhaps for other quick information extraction reasons, but should also be in the Information Service, in order to be accessed by Harvesting Services in the need of fetching records from them. The DB Service will contain ALL the information in the OIS, to be used as knowledge base for statistical caculation and as authoritative source for third-party applications interested in OpenAIRE content.
Thread. 4 – OIS: end-user access, part 1 (M6-M12, CNR, NKUA, UNIBI) This thread targets Scenario 2, search/browse. To this aim the OpenAIRE portal will be integrated with D-NET services for search and browsing functionality, which in turn rely on D-NET Index services whose content will be taken from the DB Service. The idea is to maintain a layer of Index Services containing the portion of the OIS required by the Portal. To this aim, the indices will represent a customized materialization of the OIS, calculated and extracted by querying the DB Service. By using D-NET Index Services the OpenAIRE system will be able to (i) provide full-text search and IR ranked-results and (ii) scale up to arbitrary number of accesses by keeping automated index replicas. Specifically, CNR, NKUA and UNIBI will: • Establish the structure of the data to be queried and accessed through the portal;; • Identify the queries to be run on the DB Service to extract such information;; • Configure and deploy D-NET index services and MDStore services capable of hosting the data whose data structure has been identified above;; • Manager Service for synchronizing DB service and Index Service: Build D-NET workflows capable of running the queries over the DB Service, feed the MDStores and indices with the results;; the workflows should be scheduled and executed automatically by the D-NET Manager Services;; • Manager Service for replicas: build D-NET workflows capable of keeping K replicas of MDStore Services and Index Services;; • Build the OpenAIRE Portal pages supporting search and browse through the Search Services and operating over the materialization of the OIS into Index Services.
Thread. 7 – OIS: statistics (M13-M24, NKUA, UNIBI and CERN) This thread targets Scenario 2, usage statistics. NKUA will develop Usage Statistics services matching the requirements gathered from the EC Pilot and combined with the experimentation of usage statistics harvested from institutional repositories. On the side of article and project statistics, the service will have to interact with the DB Service. It is still to be decided if the statistical data will be materialized into Index Services or calculated on demand from the DB Service.
Thread. 8 – OIS: refining the data (M13-M24, CNR, CERN, NKUA) This thread targets Scenario 1, refinement deposition (see Figure 1). Since originally it was not part of the DoW, its accomplishment could be partial. NKUA and CNR will design and develop tools giving support to end-users willing to “refine” the data while depositing into and searching and browsing from the OIS. End-users will be able to give their advice by “tagging” any record and any “field” with an action and some parameters to go with it: • Remove record or field;; • Update field;; • Add record or field;; • Merge two records;; • Split one record in two records. Administrators of OpenAIRE will have to revise, hence validate, suspend, reject or roll back all end-users actions. To this aim: • The DB Service will be extended with tables for supporting the (history of) tagging and validation model;; • The OpenAIRE portal will have to be upgraded to offer user interfaces allowing this interaction;; • D-NET authority file services will be employed to identify possible duplicates across different entities, e.g., authors. CERN will also contribute in this direction, by encapsulting duplication matching algorithms into new D-NET services specially devised for OpenAIRE. Figure 4 – Architecture of refinement deposition scenario
Thread. 10 – OIS: depositing publication metadata and file onto remote repositoriesa (M13-M24, CNR, UNIBI) This thread investigates the possibilities of metadata and file deposition from the OpenAIRE portal onto remote repositories adopting known platforms and willing to cooperate. The activities will take on from the results of the SWORD App (Simple Web-service Offering Repository Deposit) project.1
Thread. All thread to be mercerized, vat dyed fast color. Buttons: The Client Agency shall supply the gilded shirt buttons to the Contractor. The Contractor shall include the shirt buttons in a small plastic bag to be delivered with the shirt and attached to the button toggle by Client Agency. The buttons provided will be first quality gilt flat with words “State Police” and Connecticut State Seal design. Buttons shall be anchored with toggles, also washer, size 24-34 Waterbury or equal. Insignia: Connecticut State Police embroidered insignia patches to be furnished by the Client Agency shall be sewn on at the top of the sleeves within ½” from shoulder seam.
