Apply Persistent Identifier Clause Samples

Apply Persistent Identifier. In a collection management database a single physical object can be represented by several different digital assets like images, text documents, and audio files. These assets are usually not stored in the CMS itself. Assets which can be retrieved via Internet are stored on separate servers, apart from the CMS. There should be a URL or some other form of persistent identification constructed which points to the permanent location of the asset. The ECK might have to consider the provision of PIDs also for items that are not available over the web or are only internally available through the ECK to support the process. For persistency it is preferred that the PID (URI) will be provided by the CMS and stored in Europeana or an aggregator, as it is the key for updates and deletions in Europeana from the CMS of the content provider. In case the PID is source of the PID is not the CMS the ECK will have to provide the list of published PIDs back to the institutions. Other points of references like Institutions, Collections, Object-images and Linked concepts. The construction of the permanent identifier could be based on values in specific fields in the database, but the identifiers must be independent of the aggregator and persistent identifiers must remain constant for the content provider (may not vary according to the aggregator) to avoid duplicate entries. A solution for PIDs has been suggested by the HOPE project24. The re-usability of this work has to be investigated. Also, Europeana has set up a task force to define the needs of content providers regarding PIDs and the role aggregators like Europeana play to service them25. 24 ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/ 25 ▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇▇.▇▇/web/network/europeana-tech/-/wiki/Main/Task+Force+Persistent+Identifiers
View Source

Related to Apply Persistent Identifier

  • Customer Identification Program Notice To help the U.S. government fight the funding of terrorism and money laundering activities, U.S. Federal law requires each financial institution to obtain, verify, and record certain information that identifies each person who initially opens an account with that financial institution on or after October 1, 2003. Consistent with this requirement, PFPC Trust may request (or may have already requested) the Fund's name, address and taxpayer identification number or other government-issued identification number, and, if such party is a natural person, that party's date of birth. PFPC Trust may also ask (and may have already asked) for additional identifying information, and PFPC Trust may take steps (and may have already taken steps) to verify the authenticity and accuracy of these data elements.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐▇▇▇▇▇▇-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Non-Identification Approved Users agree not to use the requested datasets, either alone or in concert with any other information, to identify or contact individual participants from whom data and/or samples were collected. Approved Users also agree not to generate information (e.g., facial images or comparable representations) that could allow the identities of research participants to be readily ascertained. These provisions do not apply to research investigators operating with specific IRB approval, pursuant to 45 CFR 46, to contact individuals within datasets or to obtain and use identifying information under an 2 The project anniversary date can be found in “My Projects” after logging in to the dbGaP authorized-access portal. IRB-approved research protocol. All investigators including any Approved User conducting “human subjects research” within the scope of 45 CFR 46 must comply with the requirements contained therein.

  • Office of Supplier Diversity The State of Florida supports its diverse business community by creating opportunities for woman-, veteran-, and minority-owned small business enterprises to participate in procurements and contracts. The Department encourages supplier diversity through certification of woman-, veteran-, and minority-owned small business enterprises and provides advocacy, outreach, and networking through regional business events. For additional information, please contact the Office of Supplier Diversity (OSD) at ▇▇▇▇▇▇▇@▇▇▇.▇▇▇▇▇▇▇▇▇.▇▇▇.

  • Customer Identification Unless Elastic has first obtained Customer's prior written consent, Elastic shall not identify Customer as a user of the Products, on its website, through a press release issued by Elastic and in other promotional materials.