resourcecenter.ovid.comWolters Kluwer - Ovid Online Resources & Tools

Wolters Klus and Windows Edge. URL Information for Firewall/Proxy Administrators Ovid recommends that you allow users to connect to all of the following to ensure uninterrupted access for users: *.ovid.com *.net.jbisumari.org *.visualdx.com *.visiblebody.com *.wolterskluwer.com *.ovidds.com *.tdnet.com *.dsstatic.net *.lww.com *.wkhpe.com If that is not possible, we recommend that you allow access to the following service URLs, depending on which products you subscribe to (this is not the preferred method). Ovid termfinder.ovid.com *.oce.ovid.com wolterservices.kitaboo.com insights.ovid.com assets.ovid.com login.wolterskluwer.com stats.ovid.com linksolver.ovid.com pt.wkhealth.com ovidsp.ovid.com nursing.ovid.com ovidsp.dc1.ovid.com ovidsp.dc2.ovid.com graphics.dc1.ovid.com graphics.dc2.ovid.com acs.dc1.ovid.com acs.dc2.ovid.com nursing.dc1.ovid.com nursing.dc2.ovid.com e-bea.dc1.ovid.com e-bea.dc2.ovid.com ovid-admin.ovid.com linksolver.ovid.com odds.ovid.com odds.dc1.ovid.com odds.dc2.ovid.com oai.ovid.com webservices.ovid.com openathens.ovid.com site.ovid.com demo.ovid.com tools.ovid.com access.ovid.com resources.hlrptech.com JBI SUMARI auth.jbisumari.org sumari-prod-1.srv.jbisumari.org login.wolterskluwer.com jbi-admin.dc2.ovid.com jbiconnectplus.com connect.jbiconnectplus.org jbi-admin.dc2.ovid.com LDI watch.ondemand.org ahaplayer.ondemand.org www.audio-digest.org eJP journals.lww.com Visible Body ovid.visiblebody.com Lippincott Nursing Solutions procedures.lww.com dr-procedures.lww.com images.procedures.lww.com images.dr-procedures.com downloads.lww.com unavailable.procedures.lww.com www.lww.com advisor.lww.com competency.lww.com ceconnection.lww.com blendedlearning.lww.com lpd.lww.com lns-media.lww.com lns-services.lww.com lns-security.lww.com ns-content-service.wkhpe.com lns-media.wkhpe.com wolterskluwerhealth.d2.sc.omtrdc.net (Omniture Web Analytics) Mobile-app users that have proxy-based access to the internet: .flurry.com .appcelerator.com View Ezproxy config.txt settings for Ovid here . Note about bookmarking: If you wish to bookmark Ovid pages, please use ovidsp.ovid.com only. Including dc1”, dc2”, etc could compromise your access to Ovid. For example, do NOT bookmark URLs like these: ovidsp.dc1.ovid.com or ovidsp.dc2.ovid.com. If your network configuration requires detailing specific names, please review the following entries. If you whitelist *.ovid.com then there is no need to add these specific targets. Whitelisting the CNAMES (*.dc1.ovid.com and *.dc2.ovid.com) or *.ovid.com will be sufficient for many customers. Network traffic between Ovid and your site All network traffic from Ovid to your site should be in response to requests which users have generated. Thus, if your site is using a stateful packet inspection (SPI) firewall, you should not have to open any ports on your firewall. Email is the exception, and you should allow TCP/25 from the address ranges listed below. Should you use a non-SPI firewall, you will need to allow ephemeral (high numbered) TCP port access from the following IP address ranges. Ovid runs out of two AWS regions, EU-WEST-1 and EU-EAST-1. The AWS URL to reference for IP information: https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html#subscribe-notifications . To ensure proper delivery of email, customers are encouraged to explicitly whitelist our mail server IP addresses and e-mail accounts: 54.240.44.35, [email protected] , [email protected] , [email protected] , [email protected] , [email protected] , and [email protected] Note about Blacklists As protection against spam, it’s common for companies to enlist the use of "blacklists". Blacklists are lists maintained by independent organizations containing addresses of mail servers believed to be used to produce spam. Ovid’s mail server and the IP addresses used to send alerts included above, at times can inadvertently get listed on these blacklists. This happens because our alert system is quite popular by our customers and as such, produces enough emails that it can occasionally be mistaken for spam distribution. Unfortunately, for customers who haven’t explicitly listed our mail server IP as valid, the blacklist causes their mail server to reject connections from our mail server. Once Ovid learns of any inadvertent blacklisting, we have the IP removed from the blacklists, however we can’t guarantee it won’t end up back on them at some point in the future. To avoid problems with email delivery for users of Ovid’s AutoAlert and email functions, we strongly recommend our customers add the ranges above to be explicitly whitelisted. If you have any questions, please contact your Ovid Technical Support team. *Last Updated October 2020 Z39.50 Server Interoperability Testing Ovid Technologies is a prominent member of the Z39.50 Implementor’s Group ("ZIG") which is the standard-setting body for the Z39.50 interoperability protocol. So that other members of the Z39.50 software development community can test their clients for compatibility with the Ovid Z39.50 Server, we provide free, unlimited access to sample databases mounted on an Ovid Z39.50 Server using the latest released version of the software. The information necessary to configure any given Z39.50 client to connect to an Ovid Z39.50 Server is shown below. Consult your client software documentation to determine how to enter these parameters. If you have any questions or problems when connecting to the Ovid Z39.50 Server with a non-Ovid client, please bring them to our attention as soon as possible by emailing [email protected] . Client Configuration for Ovid Z39.50 Server Hostname z3950.ovid.com Port 210 Record Syntax USMARC SUTRS Attribute Set BIB-1 Supported Z39.50 Versions 1, 2, and 3 Supported Features Specified in option bits: Search Present Delete Set Trigger Resource Control Access Control Scan Named Result Sets Other features: AND OR AND-NOT Piggyback Present Cancel Search (via Trigger Resource Control) Security The userid and password, if specified, are ignored. Available Databases PMED - Practice MEDLINE Database ERIC - Subset of the Educational Resource Information Center Database Attribute Types USE (1): See below. RELATION (2): If specified, must be 3 ("Equal"). POSITION (3): If specified, must be 3 ("Any position in field"). STRUCTURE (4): If specified, must be 1 ("Phrase") or 2 ("Word") or 6 ("Word list"). All act the same. TRUNCATION (5): If specified, must be 100 ("Do not truncate") or 1 ("Right truncation"). The default is 100 ("Do not truncate") COMPLETENESS (6): If specified, must be 1 ("Incomplete subfield"). USE Attribute Information For each attribute, the following list specifies: USE attribute number Ovid fields searched by that USE attribute number Name of the USE attribute (according to the Z39.50-1995 standard) The test database(s) in which this attribute is valid (PMED, ERIC.) If unspecified, the attribute is valid in both test databases. 1=au,pn Personal Name 2=in Corporate Name (PMED, ERIC) 4=ti Title 5=ti TItle series 6=ti Title uniform 8=is ISSN (PMED, ERIC) 17=ui NLM Call Number 20=lm Local Classification 21=sh Subject Heading (PMED, ERIC) 25=sh MESH Subject (PMED, ERIC) 30=yr Date 31=yr Date of Publication 32=yr Date of Acquisition 33=ti Title key 34=ti Title collective 35=ti Title parallel 36=jn,ja Title Cover 37=ti Title added title page 38=ti Title caption 39=ti Title running 40=jn Title spine 41=ti Title other variant 43=ti Title abbreviated 44=ti Title expanded 45=ab Subject precis 47=me Subject subdivision (PMED) 57=au,ti Name and Title 58=cp Name geographic (PMED, ERIC) 59=cp Place Publication (PMED, ERIC) 62=ab Abstract 1000=au,ti Author-title 1002=au,pn Name 1003=au Author 1004=au Author-name personal 1005=in Author-name corporate (PMED, ERIC) 1009=pn Subject namepersonal (PMED) 1011=em Date/time added to db 1016=au,ti,ab,sh Any 1017=ui,au,in,cp,ti,ot,cm,sc,so,pb,jn,vo,ip,em,up,pg,dp,sh,pn,ab,rf,rn,is,pt,lg,sb,gs,ms,no,jc,lh,lm,as,ja,...