Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 2003 CrossRef Annual Member Meeting Technical Working Group Technical Meeting September 17, 2003 London.

Similar presentations


Presentation on theme: "1 2003 CrossRef Annual Member Meeting Technical Working Group Technical Meeting September 17, 2003 London."— Presentation transcript:

1 CrossRef Annual Member Meeting Technical Working Group Technical Meeting September 17, 2003 London

2 CrossRef Annual Member Meeting Technical Working Group Agenda 9:00 - 9:05 Introduction 9:05 - 9:30 Review of system operation, configuration & issues 9:30 -10:00 TOC Syndication Using RSS Tony Hammond, Elsevier 10: :15 Coffee Break 10: :15 New system features 11: :45 Related technology topics 11:45 - ? Open discussion

3 CrossRef Annual Member Meeting Technical Working Group Operational Issues Current configuration and planned changes System utilization / query response times Conflicts Schema Issues Procedures Misc. (special characters, getting XML, reports …) Where to get help

4 CrossRef Annual Member Meeting Technical Working Group Current Configuration & Planned Changes Dell 2650 Java Web / synch queries Batch processing - deposits - asynch queries Sun E Mhz Sparc II 4GB Mem Oracle Database 100 Mb switch 10 Mb full dup Planned changes Replace the database machine with a faster Sun box and better disks Add a load balancer (service) on the front end so the Web component can run on more than one machine (good reason to switch to Add a shadow ethernet drop from the co-location facility

5 CrossRef Annual Member Meeting Technical Working Group System Utilization Sat Sun Mon Tue Wed Thu Fri System utilization driven by database use Operations Availability (1/03 – 8/03): 97.6% Performance : 1 successful query = avg. response time is seconds 1 failed query = avg. response time is 1.2 seconds Deposit performance depends on number of jobs in the Q (4 simultaneously) (50% 24hr)

6 CrossRef Annual Member Meeting Technical Working Group System Utilization Query response time Sat Sun Mon Tue Wed Thu Fri

7 CrossRef Annual Member Meeting Technical Working Group System Utilization Query response time Sat Sun Mon Tue Wed Thu Fri

8 CrossRef Annual Member Meeting Technical Working Group Conflicts A conflict is created when 2 (or more) DOIs are deposited with the same metadata Journal / Author / Volume / Issue / Page / Article Title / Sequence-Number Happens when: No page numbers available Limited meta-data (no author or article title) Same article title (Book Reviews) on the same page (no author) Two publishers host the same article Publisher wants to assign a new DOI (naming convention change) What can be done about them Re-deposit one of the DOIs and change the meta-data (auto-resolve) An administrator can erase the conflict (both DOIs remain as peers) A meta-data search will yield no (ambiguous) results or multiple hits An administrator can make one the prime and the other an alias The alias is essentially deleted, it can never be updated again (unless we do an un-do) Ok Bad Ok?

9 CrossRef Annual Member Meeting Technical Working Group /j x Added with conflict /j x Conflicts What you see in your log

10 CrossRef Annual Member Meeting Technical Working Group Conflicts The conflict report (we them now, soon to be available on Conflict report for created on Jul 24,2003 =========================================== ConfID: 105 CauseID: OtherID: 1711, JT: Analytica Chimica Acta MD: Louwerse, 346,3,285,1997,Monitoring time-varying concentrations in sample streams by multiple input chromatography DOI: /S (97) (105-null ) DOI: /S (97) (105-null ) =========================================== … ======== Number Of Conflicts: ========

11 CrossRef Annual Member Meeting Technical Working Group Conflicts Un-resolved conflicts (as of July 24) PrefixCount

12 CrossRef Annual Member Meeting Technical Working Group Schema Issues Versions Currently at 2.0.5, several small changes have been made to bring the schema to (do not include the minor rev # in the declarations) When a major change occurs (like forward linking) the schema will be revised and you must change the declaration to pick up the changes (the system will recognize multiple schemas)

13 CrossRef Annual Member Meeting Technical Working Group Schema Issues Character entities Schema does (generally) not do character entities Xerces will understand certain basic Latin & < > " For others you must numerically encode them Greek small letter alpha => α or α

14 CrossRef Annual Member Meeting Technical Working Group Schema Parser

15 CrossRef Annual Member Meeting Technical Working Group Schema Parser

16 CrossRef Annual Member Meeting Technical Working Group Procedures DOI Ownership Transfer When a journal is transferred between two publishers 1)Notify CrossRef via , supply journal title, old and new prefix 2)Supply a list of DOIs (CrossRef can generate the list if needed) 3)Supply new URLs (if needed) 4)CrossRef processes transfer - changes ownership in CrossRef MDDB - changes administration in handle system DOI Changes & Conflict Resolution When a new DOI is to be assigned to replace another DOI (due to error or the need to restructure the suffix composition) 1)Construct an XML deposit file for the new DOIs (same metadata as the old DOIs) 2)Deposit it, examine the log for conflict warnings 3)Contact CrossRef so an administrator can overwrite the old DOIs with the new DOIs - deprecates old DOI in MDDB - aliases old DOI to new DOI in handle system

17 CrossRef Annual Member Meeting Technical Working Group aamr amerindhyg amet amonh ams apha arnold aspbs biomedcen brill brps cabi cup dekker ediciones elsevier eurrespsoc fdcomm funinapr geosociety hhs hhs-mosby hindawi ilsi inschemeng isas jmry karger lawerl librapharm lww maney maryanne mcb mit nature pengp pharmapress ppress roysocmed sage schweiz sivb springer taylor urfi wiley wscientific Schema Issues Publishers Still Using the DTD

18 CrossRef Annual Member Meeting Technical Working Group Special Characters , | Journal of Physics B Atomic Molecular and Optical Physics| Trábert|36|6|1129|2003| full_text||10.108/ /36/6/305 Trábert: [0]=0x54,[1]=0x72,[2]=0xa0,[3]=0x62,[4]=0x65,[5]=0x72,[6]=0x7 Tr bert #160 = #xA , |Journal of Physics B Atomic Molecular and Optical Physics|Tr bert|36|6|1129|2003|full_text|| / /36/6/ / /36/6/305 In a Browser (IE 6.0) In a DOS command window The query: |j phys B at mol opt phys||36||1129|||| Byte string of the authors name What was deposited

19 CrossRef Annual Member Meeting Technical Working Group , |Journal of Physical Organic Chemistry |ChciDska|16|4|213|2003|full_text|| /poc.596 ChciDska: [0]=0x43,[1]=0x68,[2]=0x19,[3]=0x63,[4]=0x69,[5]=0x44, [6]=0x73,[7]=0x6b,[8]=0x61 Chęcińska In a Browser (IE 6.0) In a DOS command window The query: |j phys org chem||16||213|||| Byte string of the authors name What was deposited , |Journal of Physical Organic Chemistry|ChciDska|16|4|213|2003|full_text|| /poc /poc.596 0x19 is unprintable, 0x44 is a D Special Characters

20 CrossRef Annual Member Meeting Technical Working Group Special Characters

21 CrossRef Annual Member Meeting Technical Working Group … /poc.596 Chęcińska 2003 Special Characters

22 CrossRef Annual Member Meeting Technical Working Group Getting the XML for DOIs In order to update meta-data you need to have the XML An update is a complete re-write, omitted fields in the update are removed from the database The update can be in Schema even if the original deposit was in DTD CrossRef can now retrieve the XML for a list of DOIs. DOIs can be from different submissions Extracted XML will be in the same format as the deposit/update the list of DOIs to

23 CrossRef Annual Member Meeting Technical Working Group Depositor Report

24 CrossRef Annual Member Meeting Technical Working Group Query Formulation Journal queries differ from Conference Proceedings and Book queries For Conference Proceedings : SER_TITLE => (one, optional) VOL_TITLE => (must have one) Note: is not searchable For Books: SER_TITLE => > VOL_TITLE => (1..6 of either of these) Note: is not searchable Journals: ISSN |TITLE/ABBREV | FIRST AUTHOR| VOLUME | ISSUE | START PAGE | YEAR | RESOURCE TYPE | KEY | DOI Books and conference proceedings : ISBN/ISSN | SER_TITLE | VOL_TITLE | AUTHOR/EDITOR | VOLUME | EDITION_NUMBER | PAGE | YEAR | COMPONENT_NUMBER | RESOURCE_TYPE | KEY | DOI Note: For series titles to matter you must assign them a DOI when depositing

25 CrossRef Annual Member Meeting Technical Working Group Where to get help How to get started How to deposit How to query System help pages (more technical)

26 CrossRef Annual Member Meeting Technical Working Group RSS And TOCs

27 CrossRef Annual Member Meeting Technical Working Group New System Features Tracking IDs XML Query Format Enhanced XML Results Forward Matching Forward Linking Real Time Queries

28 CrossRef Annual Member Meeting Technical Working Group Tracking IDs & pwd= &doi_batch_id= &type=result { "@context": "http://schema.org", "@type": "ImageObject", "contentUrl": "http://images.slideplayer.com/708967/2/slides/slide_27.jpg", "name": "28 2003 CrossRef Annual Member Meeting Technical Working Group Tracking IDs http://doi.crossref.org/servlet/submissionDownload?usr= & pwd= &doi_batch_id=2003-08-11-1016008&type=result

29 CrossRef Annual Member Meeting Technical Working Group Tracking IDs

30 CrossRef Annual Member Meeting Technical Working Group XML Query Format Problem: Piped queries can be awkward to deal with and not extensible Solution: Create an XML schema for queries To use some of the new CrossRef features you must query using this format Request multiple hits Request forward matching Turn off fuzzy matching (on a field by field basis) Use tracking Ids on query jobs Match on NULL fields

31 CrossRef Annual Member Meeting Technical Working Group Enhanced XML Query Results Problem: We wanted to supply more information about the query results Solution: Create an extended XML schema for query results The existing XML query result format is still available (no schema or DTD) Results in this format can show Multiple hits – when the metadata search resolved to more than one DOI (ambiguous results produce NO match in a normal query) Fuzzy matching indicators

32 CrossRef Annual Member Meeting Technical Working Group Input SomeTrackingID1 Develop. Dynamics Output { "@context": "http://schema.org", "@type": "ImageObject", "contentUrl": "http://images.slideplayer.com/708967/2/slides/slide_31.jpg", "name": "32 2003 CrossRef Annual Member Meeting Technical Working Group Input hisham@atypon.com SomeTrackingID1 Develop.", "description": "Dynamics 223 426 2002 Output

33 CrossRef Annual Member Meeting Technical Working Group Forward Matching Problem: Members must re-query CrossRef to find DOIs from recent deposits Solution: Create a stored query mechanism where CrossRef remembers failed queries, who sent them and notifies them when a deposit resolves them Request forward matching in the query { "@context": "http://schema.org", "@type": "ImageObject", "contentUrl": "http://images.slideplayer.com/708967/2/slides/slide_32.jpg", "name": "33 2003 CrossRef Annual Member Meeting Technical Working Group Forward Matching Problem: Members must re-query CrossRef to find DOIs from recent deposits Solution: Create a stored query mechanism where CrossRef remembers failed queries, who sent them and notifies them when a deposit resolves them Request forward matching in the query Develop.", "description": "Dynamics 223 426 2002.", "width": "800" }

34 CrossRef Annual Member Meeting Technical Working Group Forward Matching Each stored query is identified by user assigned attributes The query must be given a unique key The request must have a unique batch-id Identical queries are stored once, multiple users may be associated with one query When a stored query matches an is sent with the XML results (one per query) Users may poll for stored queries that have matched usr= &pwd= & startDate= &endDate= Start and end dates are inclusive. Must be formatted a yyyy-mm-dd

35 CrossRef Annual Member Meeting Technical Working Group Forward Matching Processing Forward Matches 1.Upon receipt the query (if it initially fails) is sorted based on title 2.When deposits are made, titles trigger corresponding stored queries 3.Batch job will be run nightly to process all triggered stored queries 4.If the batch does not complete in the allowed window it will pick up from where it left off in the next interval 5.Weekend intervals will be longer than weekday intervals

36 CrossRef Annual Member Meeting Technical Working Group Forward Linking A new service to be deployed by year end (pending board final approval) Allow the retrieval of DOIs for articles that cite another article Builds on existing CrossRef transactions Publishers deposit metadata for their articles Publishers query for the references in those articles to get DOIs If CrossRef knows which references go with which articles we can tell owners of the cited articles who cites them

37 CrossRef Annual Member Meeting Technical Working Group Forward Linking

38 CrossRef Annual Member Meeting Technical Working Group Forward Linking Include the list of references with the article when registering the DOI Combine deposit and query into one step Or, upload a list of references for an article Example: [source document DOI] tab [||||||||reference DOI] [source document DOI] tab [issn|journal|author|volume|issue|page|year] [source document DOI] tab [reference DOI] … Constraints: The source document DOI must exist in CrossRef prior to using this method. If the reference is supplied as a DOI, that DOI must exist in CrossRef For bulk loads no metadata query results will be returned. One cited reference per line

39 CrossRef Annual Member Meeting Technical Working Group Forward Linking Forward links (aka. Cited-By lists) will be retrieved by a simple query Send in the DOI of the target article (a new HTTP request) Receive an extended set of meta-data (in an XML response) for each of the citing articles NameComment Full Journal Title Abbreviated Journal Title ISSNsMore than 1 Journal DOI Article TitleRequired element in schema deposits Contributors All authors, given and surname up to a max of 10 (when >10 list as et al) Volume Issue PagePage range Article DOI Article Identifier or

40 CrossRef Annual Member Meeting Technical Working Group Real Time Queries Real time queries are done on-the fly When a user clicks on a link When the page is constructed for display The current HTTP GET interface is being used by some for real time queries No guaranteed level of service BUT for single queries 1 second response Does place an un-intended load on the system A premium query service will be available that operates on a different interface Better, more deterministic access to the CrossRef system Less overhead than the synchronous HTTP GET interface In testing now!

41 CrossRef Annual Member Meeting Technical Working Group The Handle System Parameter Passing Open URL Local Link Servers Multiple Resolution Related Technologies

42 CrossRef Annual Member Meeting Technical Working Group The Handle System What is it ? A network accessible database for retrieving name-value pairs A hash where the DOI is the key A system built by CNRI and licensed for use by the IDF (DOI)CNRI How does DOI / CrossRef use it ? CrossRef is a service to input and update the name-value pairs is a resolver that knows what we want to do with DOIs DOI could (and may someday) operate on any look-up mechanism For key=10.xxxx/yyyy retrieve the name-value pair called URL and redirect to the value string (which should be a URL) Important: DOI and Handle are not the same thing! DOIs are handles which are intended to behave a certain way

43 CrossRef Annual Member Meeting Technical Working Group The Handle System

44 CrossRef Annual Member Meeting Technical Working Group 0004 The Handle System

45 CrossRef Annual Member Meeting Technical Working Group OpenURL and DOIs/CrossRef CrossRef helps solve the appropriate copy problem by providing a reverse DOI lookup (DOI in / meta-data out) id= /jmbi &pid= : CrossRef offers an OpenURL 1.0 compliant resolver : &aulast=Maas LRM &title= JOURNAL OF PHYSICAL OCEANOGRAPHY&volume=32 &issue=3 &spage=870&date=2002 (This resolver will redirect you to the target document) OpenURL and DOI are complementary technologies

46 CrossRef Annual Member Meeting Technical Working Group example.org? Start with the BaseURL url_ver=z &url_ctx_fmt=ori:fmt:kev:mtx:ctx &rft_id=ori:doi: /science &rft_id=ori:pmid: &rft_val_fmt=ori:fmt:kev:mtx:journal &rft.genre=article &rft.atitle=Isolation of a common receptor for … &rft.jtitle=Science &rft.aulast=Bergelson &rft.auinit=J … Add the fixed elements Add the referrer Add the referent &rfr_id=ori:rfr:publisher.com Identifier for referrer OpenURL Referrer Domain of referrer Version Declare ContextObject format Include identifiers Declare the metadata format Shows referent (rft) format (fmt) is by value (val) Indicates we are using key- encoded-values (kev) as defined in the journal matrix (mtx) in the registry. Add the metadata elements Substitute actual values for the item being referenced What does an OpenURL look like

47 CrossRef Annual Member Meeting Technical Working Group A&I (Ovid) as link source Link SourceLink MenuLink Target

48 CrossRef Annual Member Meeting Technical Working Group OpenURL Aware OpenURL Linking: SFX & CrossRef References DOI Server Server DOI OpenURL Metadata DOI link doi= /j x doi= /j x

49 CrossRef Annual Member Meeting Technical Working Group Multiple Resolution

50 CrossRef Annual Member Meeting Technical Working Group Multiple Resolution Re Hosted journal (the appropriate copy problem) 1.Publisher A produces and hosts a journal from 1999 through Publisher B acquires the journal in 2003 and hosts all back issues Pre 2003 DOIs are transferred to publisher B and the URLs are reset to publishers Bs 3.A customer subscribes to publisher A and wants to go there for pre issues. Journal available from more than one site (not a mirror) Availability of alternative services (print, rights clearance …) Supplemental material Manifestations & Relations

51 CrossRef Annual Member Meeting Technical Working Group Multiple Resolution – things to consider Multiple resolution is not always desirable (probably most of the time) In some contexts the link should behave as a single resolution Implementation concerns Impact on the publishers Web site must be small (display and behavior) Resolution process first step (when the user clicks) must be fast Large data transfers may not be practical (link updates) Do not place too high a load on any single point (i.e. Handle) Policy concerns Access control (who can get on the MR lists for a item) Action control (who decides when MR will be available to the user) Quality control (who monitors landing page behavior)

52 CrossRef Annual Member Meeting Technical Working Group Multiple Resolution – what's next CrossRef and Copyright Clearance Center have started a prototype A white paper to be released this fall Define the operational issues Define the governance issues Present possible technical options Construct a demonstration prototype Not a fully functional solution

53 CrossRef Annual Member Meeting Technical Working Group Multiple Resolution The technical issues are surmountable The political and business case issues will be much more difficult

54 CrossRef Annual Member Meeting Technical Working Group CrossRef Technical Working Group Join the TWG !!! Monthly teleconferences Mailing list Mail list archives available on Planning an in-person TWG for later this year


Download ppt "1 2003 CrossRef Annual Member Meeting Technical Working Group Technical Meeting September 17, 2003 London."

Similar presentations


Ads by Google