Metadata and Industry Standards Sample Clauses

Metadata and Industry Standards. 5.1 When provided by the Eligible Author, Xx Xxxxxxx undertakes to use ORCID (xxxx://xxxxx.xxx/) throughout the workflow from submission to publication, expose Eligible Authors’ ORCID ID in Eligible Articles and distribute it to Abstracting & Indexing (A&I) services, CrossRef and other discovery services. 5.2 Upon publication of an Eligible Article, De Gruyter will register as much metadata as possible on CrossRef, including, but not limited to: (1) the Eligible Article’s digital object identifier (DOI), (2) the funding metadata, including funder name and grant number, in the metadata in Funder Registry (on CrossRef), (3) bibliographic citations, (4) funder of the open access publication and (5) the Open Access License. 5.3 De Gruyter is responsible for updated and clear information at the DOAJ and SHERPA/RoMEO websites. 5.4 De Gruyter will comply with the last version of XXXX’s Recommended Practice on Access and Licensing Indicators (xxxxx://xxx.xxxx.xxx/standards-committees/access-and- license-indicators), including, but not limited to, guidance regarding free_to_read and license_reference metadata fields and regarding mechanisms for distributing metadata.
Sample 1
AutoNDA by SimpleDocs
Metadata and Industry Standards. 3.5.1 Licensor should undertake to use the ORCID ID (xxxx://xxxxx.xxx/) throughout the workflow from submission to publication and include Eligible Authors’ ORCID ID in Eligible Articles and via Abstracting & Indexing (A&I) services and other discovery services, to the extent provided by the Eligible Author. However, the parties agree that due to developments at Licensor’s current publishing workflows, the foregoing may not be available and there is no obligation of Licensor to use the ORCID ID. It is the Eligible Author’s responsibility to provide all necessary details in respect of his/her ORCID ID to the Licensor. 3.5.2 Upon publication of an Eligible Article, Licensor will register the article metadata on CrossRef, including, but not limited to: (1) the Eligible Article’s digital object identifier (DOI), (2) the funding metadata, including funder name and grant number, in the metadata in Funder Registry (on CrossRef), (3) bibliographic citations, (4) to the extent supported by CrossRef and if Licensor’s workflows support so, funder of the open access publishing as defined in clause 3.6.1 and (5) the Open Access License if, in each case of the above, CrossRef accepts the specific metadata, and if provided by the author at submission. 3.5.3 Licensor will comply with the last version of NISO’s Recommended Practice on Access and Licensing Indicators (xxxxx://xxx.xxxx.xxx/standards-committees/access-and-license-indicators), including, but not limited to, guidance regarding free_to_read and license_reference metadata fields and regarding mechanisms for distributing metadata.
Sample 1
Metadata and Industry Standards. When provided by the Eligible Author, Publisher undertakes to use ORCID (xxxx://xxxxx.xxx/) throughout the workflow from submission to publication and expose Eligible Authors’ ORCID ID in Eligible Articles and via Abstracting & Indexing (A&I) services, CrossRef and other discovery services. o Upon publication of an Eligible Article, Publisher will register as much metadata as possible on CrossRef, including, but not limited to: (1) the Eligible Article’s digital object identifier (DOI), (2) the funding metadata, including funder name and grant number, in the metadata in Funder Registry (on CrossRef),
Sample 1
Metadata and Industry Standards. 7.1. The Licensor undertakes to use the ORCID ID (xxxxx.xxx) throughout the workflow from submission to publication and include Eligible Authors’ ORCID ID in Eligible Articles and via Abstracting & Indexing (A&I) services and other discovery services in accordance with Licensee, to the extent provided by the Eligible Author. It is the Eligible Author’s responsibility to provide all necessary details in respect of his/her ORCID ID to the Licensor. This Section does not apply to Non-Standard Journals. 7.2. Upon publication of an Eligible Article, Licensor will register the article metadata on CrossRef, including, but not limited to: (1) the Eligible Article’s digital object identifier (DOI), (2) the funding metadata, including funder name and grant number, in the metadata in Funder Registry (on CrossRef), (3) bibliographic citations, (4) to the extent supported by CrossRef and if Licensor’s workflows support so, funder of the open access publishing as defined in Section 8.1 and (5) the Open Access License if, in each case of the above, CrossRef accepts the specific metadata, and if provided by the author at submission. 7.3. Licensor will comply with the last version of XXXX’s Recommended Practice on Access and Licensing Indicators (xxxxx://xxx.xxxx.xxx/standards-committees/access-and-license-indicators), including, but not limited to, guidance regarding free_to_read and license_reference metadata fields and regarding mechanisms for distributing metadata.
Sample 1
Metadata and Industry Standards a) When provided by the submitting author and integrated into the manuscript submission system, Publisher undertakes to use ORCID (xxxx://xxxxx.xxx/) throughout the workflow from submission to publication and expose Eligible Corresponding Authors’ ORCID ID in the articles and via Abstracting & Indexing (A&I) services, CrossRef and other discovery services. b) Upon publication, Publisher will register as much metadata as possible on CrossRef, including, but not limited to: (1) the article’s digital object identifier (DOI), (2) the funding metadata (if provided by the author), including funder name and grant number, in the metadata in Funder Registry (on CrossRef), (3) bibliographic citations (4) funder of the open access publication and, (4) as of 2021, the applicable CC licence. c) Publisher is responsible for updated and clear information at the DOAJ and SHERPA/RoMEO websites.
Sample 1

Related to Metadata and Industry Standards

  • Industry Standards Supplier will implement appropriate technical and organizational security measures that comply with Industry Standards in all applicable goods, services, equipment, software systems and platforms that Supplier uses to access, process and/or store Accenture Data. “Industry Standards” means security measures that are commercially reasonable in the information technology industry and that are designed to ensure the security, integrity, and confidentiality of Accenture Data, and to protect against Security Incidents.

  • Quality Standards Each Party agrees that the nature and quality of its products and services supplied in connection with the other Party's Marks will conform to quality standards set by the other Party. Each Party agrees to supply the other Party, upon request, with a reasonable number of samples of any Materials publicly disseminated by such Party which utilize the other Party's Marks. Each Party will comply with all applicable laws, regulations, and customs and obtain any required government approvals pertaining to use of the other Party's marks.

  • Safety Standards Performance of the Contract for all commodities or contractual services must comply with requirements of the Occupational Safety and Health Act and other applicable State of Florida and federal requirements.

  • Design Criteria and Standards All Projects/Services shall be performed in accordance with instructions, criteria and standards set forth by the Director.

  • Industry Data The statistical and market-related data included in each of the Registration Statement, the Pricing Disclosure Package and the Prospectus are based on or derived from sources that the Company reasonably and in good faith believes are reliable and accurate or represent the Company’s good faith estimates that are made on the basis of data derived from such sources.

  • Technical Requirements 4.5.3.1 Tandem Switching shall have the same capabilities or equivalent capabilities as those described in Telcordia TR-TSY-000540 Issue 2R2, Tandem Supplement, June 1, 1990. The requirements for Tandem Switching include but are not limited to the following: 4.5.3.1.1 Tandem Switching shall provide signaling to establish a tandem connection; 4.5.3.1.2 Tandem Switching will provide screening as jointly agreed to by <<customer_short_name>> and BellSouth; 4.5.3.1.3 Where applicable, Tandem Switching shall provide AIN triggers supporting AIN features where such routing is not available from the originating end office switch, to the extent such Tandem switch has such capability; 4.5.3.1.4 Where applicable, Tandem Switching shall provide access to Toll Free number database; 4.5.3.1.5 Tandem Switching shall provide connectivity to Public Safety Answering Point (PSAP)s where 911 solutions are deployed and the tandem is used for 911; and 4.5.3.1.6 Where appropriate, Tandem Switching shall provide connectivity for the purpose of routing transit traffic to and from other carriers. 4.5.3.2 BellSouth may perform testing and fault isolation on the underlying switch that is providing Tandem Switching. Such testing shall be testing routinely performed by BellSouth. The results and reports of the testing shall be made available to <<customer_short_name>>. 4.5.3.3 BellSouth shall control congestion points and network abnormalities. All traffic will be restricted in a non-discriminatory manner. 4.5.3.4 Tandem Switching shall process originating toll free traffic received from <<customer_short_name>>’s local switch. 4.5.3.5 In support of AIN triggers and features, Tandem Switching shall provide SSP capabilities when these capabilities are not available from the Local Switching Network Element to the extent such Tandem Switch has such capability.

  • Minimum Necessary Standard Business Associate shall apply the HIPAA Minimum Necessary standard to any Use or disclosure of PHI necessary to achieve the purposes of this Contract. See 45 CFR 164.514 (d)(2) through (d)(5).

  • Quality Management System Supplier hereby undertakes, warrants and confirms, and will ensue same for its subcontractors, to remain certified in accordance with ISO 9001 standard or equivalent. At any time during the term of this Agreement, the Supplier shall, if so instructed by ISR, provide evidence of such certifications. In any event, Supplier must notify ISR, in writing, in the event said certification is suspended and/or canceled and/or not continued.

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • Registry Services “Registry Services” are, for purposes of the Agreement, defined as the following: (a) those services that are operations of the registry critical to the following tasks: the receipt of data from registrars concerning registrations of domain names and name servers; provision to registrars of status information relating to the zone servers for the TLD; dissemination of TLD zone files; operation of the registry DNS servers; and dissemination of contact and other information concerning domain name server registrations in the TLD as required by this Agreement; (b) other products or services that the Registry Operator is required to provide because of the establishment of a Consensus Policy as defined in Specification 1; (c) any other products or services that only a registry operator is capable of providing, by reason of its designation as the registry operator; and (d) material changes to any Registry Service within the scope of (a), (b) or (c) above.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!