JP2012501490A - Method and apparatus for generating a standard document identifier from a content reference - Google Patents

Abstract

Use domain names of websites where knowledge workers are working to obtain domain specific parser programs. The parser program is then sent back to the browser where the knowledge worker is browsing the information to extract the content metadata from the website where the knowledge worker is working. In one embodiment, the parser program extracts content metadata from web pages displayed in the browser. In another embodiment, the parser program navigates from a web page displayed in the browser to another web page containing content metadata, and extracts content metadata from the other page. In yet another embodiment, the content metadata, such as the issue title, returned to the Rights Advisor website through the parser is “normalized” to obtain a standard identifier and uses that standard identifier. Thus, the content right is determined.

Description

  The present invention relates to a method and apparatus for determining digital copyright indication and content reuse rights to which multiple licenses and subscriptions apply. The work, or “content”, is created by the author, but is generally subject to legal restrictions regarding reuse. For example, most content is protected by copyright. In order to comply with copyright laws, content users often obtain content reuse licenses. The content reuse license is actually a “bundle” of rights including the right to express the content in different formats, the right to reproduce the content in different formats, the right to produce derivative works, and so on. Thus, depending on the particular reuse, a unique license for reuse will have to be obtained.

  Many organizations use content for a variety of purposes, including research and knowledge labor. These organizations obtain content via a number of channels, such as purchasing content directly from publishers, purchasing content from subscription resellers via subscriptions, and so on. A subscription typically includes a number of reuse rights that are transferred to subscribers. A given subscription service generally seeks to provide default rights for the entire subscription, but many customers often negotiate with the service to obtain additional rights. Accordingly, the reuse right varies depending on the subscription, and the reuse right available for a specific subscription may vary depending on the issue even within the scope of the subscription. In addition, reuse rights transferred in these subscriptions often overlap with other rights and licenses purchased from license clearinghouses or from other publishers.

  Many knowledge workers try to determine which rights are valid for a piece of content before using it, so as not to infringe the rightful rights of the right holder. Currently, however, determining what reuse rights an organization has for any given issue is a time consuming manual process, typically obtained from the content provider, and other sources Requires a librarian or attorney to review all license agreements purchased from the site and any potential licensing related to its use prior to use. Since this determination is difficult, payment for the right has already occurred, and excessive spending may be required to purchase the right. Alternatively, knowledge workers assume that the organization has a license for reuse rights, but do not actually have the risk that knowledge workers will violate reuse rights.

  One issue in determining which rights apply to a given issue is to be able to examine the correct contract to determine what rights are available to the organization. In other words, the issue is tied to one or more contracts that transfer rights. One prior art method for making this connection is to embed a special “tag” in the publication. For example, when a publication is later opened for investigation, the tag can be activated to direct the user to a designated location where the rights agreement is located, such as a website. This contract requires each issue to include a special tag for the duration of the contract. This is feasible for newly issued publications, but republishing older publications with special tags would be prohibited. Therefore this system cannot be used for many existing publications.

  Many users who seek the location of the rights of a publication have only a universal resource locator of the publication, i.e., a URL associated with the publication. The primary purpose of such a URL is to indicate where on the network, such as the Internet, where a copy of the publication can be found. Thus, the URL usually does not directly identify the issue itself. On the other hand, many URLs contain information useful for identifying the issue. However, there is currently no standard URL configuration in which such useful information can be found at various locations within the URL depending on the publisher or clearinghouse. Further, such useful information may be coded in various ways. Therefore, it is difficult to extract information from a specific URL.

  In yet another case, even a URL cannot be used. Only basic information such as the title of the issue, the author, the work that contains the issue, and the year of issue, or some combination of the above information can be seen in the text of the web page that the worker is browsing. . Alternatively, the publication that the operator is browsing may include a reference to another web page, such as a summary or document list page containing the information described above. Since each of these web pages has a different special format, it can even determine where on the individual page the information needed to identify the available rights (called content “metadata”) should be looked for Difficult to do.

  In accordance with the principles of the present invention, the domain name of the website on which the knowledge worker is working is sent to the website of the rights advisor. The Rights Advisor website uses the domain name to obtain a domain-specific parser program. The parser program is then sent back to the browser where the knowledge worker is browsing the information to extract the content metadata from the website where the knowledge worker is working. The extracted content metadata is returned to the rights advisor website and used to determine the rights associated with the publication.

  In one embodiment, the parser program extracts content metadata from web pages displayed in the browser.

  In another embodiment, the parser program navigates from a web page displayed in the browser to another web page containing content metadata and extracts content metadata from the other page.

  In yet another embodiment, content metadata, such as issue titles, returned from the Rights Advisor website via a parser is “normalized” to obtain a standard identifier and uses that standard identifier. Thus, the content right is determined.

  In yet another embodiment, when a URL is associated with the content, the Rights Advisor website attempts to search for the standard identifier of the content using that URL, while at the same time being unique to the website domain; Attempt to obtain a parser program that can find information related to content on a web page.

1 is a block schematic diagram showing the basic architecture of an inventive rights allocation system in a high level form. It is a figure which shows the table arrangement | sequence in the database for memorize | storing bookmarklet script information. It is the typical screen display represented by the conventional search engine in a web browser. It is a figure which shows the typical display of the content searched by a search engine, when the keyword "nature methods" is input into the text box. This drawing shows a hyperlink to the rights advisor web page. FIG. 6 is a flow chart showing the steps in an exemplary process for determining and resolving the type of usage rights required. It is a block schematic diagram which illustrates the component of a contract. It is the block schematic diagram which illustrates the component in the identifier search apparatus of issue. FIG. 8B is a flowchart illustrating steps in an exemplary process for searching for an issue identifier that is executed by the apparatus illustrated in FIG. 7 together with FIG. 8B. FIG. 8B is a flowchart illustrating steps in an exemplary process for searching for an issue identifier that is executed by the apparatus illustrated in FIG. It is a figure which shows the table arrangement | sequence in the database for memorize | storing a URL parser and a metadata parsing script. FIG. 5 shows a screenshot of a periodicals website where an ISSN (International Standard Serial Number) identifier is embedded in the page. It is a figure which shows the HTML code used in order to display the web page shown in FIG. 10 on the conventional web browser, and how to parse such a web page and take out an identifier.

  FIG. 1 is a block schematic diagram illustrating one embodiment 100 constructed in accordance with the principles of the present invention. In some cases, the customer can use a conventional search engine in the web browser 102 to search for content and display the content in the display area 103. By downloading a small executable program called a “bookmarklet”, the web browser 102 has been modified to allow the browser to interact with the “rights advisor” web server in accordance with the principles of the present invention. Such a program can be, for example, a JavaScript program, which is specific for a particular URL domain or set of URL domains.

  FIG. 2 illustrates a set of database tables 200 for storing script text corresponding to various bookmarklet scripts. These tables include a URL basic key table 204 for specifying URL map keys, and each URL map key identifies a set of URLs to which a particular bookmarklet script is applied. Each record of the basic key table 204 includes a URL map key identifier (URL_MAPKEY_ID), a map key name (URL_MAPKEY_BASE), and an identifier (BOOKMARKMARK_SCRIPT_ID) that specifies a specific bookmarklet text to be applied to the map key. The URL domain that is an element of each domain map is specified in the URL domain table 206. Records are stored in the URL domain table 206. Each record includes a URL domain identifier (URL_DOMAIN_ID), a map key identifier (URL_MAPKEY_ID) designating a domain map to which the domain belongs, a domain name (URL_DOMAIN), and a URL configuration file (URL_CONFIG_XML). , The main parser identifier (URL_PRIMARY_PASER), and the identifier of the associated bookmarklet script (BOOKMARKLET_SCRIPT_ID). When a bookmarklet script is specified for a particular domain, it takes precedence over any script specified for the domain map to which that domain belongs.

  The bookmarklet script is specified in the bookmarklet script table 208. Each record of the table 208 includes a script identifier (SCRIPT_ID), a key for selecting a specific script (SELECT_KEY), an index indicating whether or not the script is valid, and how to download and execute the script. Stores various timing and retry parameters used. The actual script text is stored in the version control text table 210. This version control text table stores records, and each record includes a text identifier (VTEXT_ID), a text type (VTEXT_TYPE_ID), a revision number (REVISION_NUM), and an actual text (CONTENT). This text table stores both script text and URL structure as shown in the type field. If the script is changed, the record is not overwritten. Instead, a new record is inserted into the text table. This allows review and reversion of previous script versions as needed.

  FIG. 3 shows a typical screen display represented by such a search engine. The web browser 300 includes a search field 302 that includes a text box 304 for accepting a search term and a command button 306 for launching a search for a publication having text that includes the search term. Is included. Web browser 300 has been modified in accordance with the principles of the present invention to include a small executable program called a “bookmarklet” that causes the browser to interact with a “rights advisor” program.

  FIG. 4 shows an exemplary display of content placed by the search engine when the keyword “nature methods” is entered into the text box 404 in the search field 402 of the browser 400 and the command button 406 is selected. . The search results are shown as a plurality of rows 408 to 418 in the list box 407. Each line includes information about an article searched by the search. The search engine illustrated in FIG. 4 displays information including the title of the article, the publisher, and the standard identification number associated with the publication that contains the article.

  In each article, that information is associated with a hyperlink generated by a bookmarklet that allows the user to place and display the rights associated with the article. For example, row 408 includes a hyperlink 420 that allows the user to search and display the rights to articles of “Nature Methods” displayed within that row. Similarly, lines 410 to 418 include hyperlinks 422 to 430 for searching and browsing for rights associated with articles displayed in those lines.

  Apart from this, the URL related to the article may not refer to the publisher or the publication containing the article. For example, the user may be examining the full text of a document that contains URLs that indicate URLs that indicate different parts of the document or URLs that list text that identifies the publisher and issue. Alternatively, the full text page of the document may not contain any URL. Instead, text identifying the publisher and issue, or a URL indicating the publisher and issue, can be placed on another web page, for example, on the literature list page or the first document information page. The arrangement and format of the information is generally specific to an individual domain or website, and may be all that is available only for the URL of the website, including the domain. However, in accordance with the principles of the present invention, articles can be identified by parsing URLs or searching for article identification information embedded in other text information on a web page. Furthermore, the URL parsing mechanism and text search can be tailored for each domain so that various formats can be adapted.

  Returning to FIG. 1, when a hyperlink is selected, the bookmarklet 104 causes the web browser 102 to access the rights advisor web page 108 hosted by a server located in the rights clearinghouse. When the web page 108 is accessed, the bookmarklet is a unique bookmarklet that is used to identify the element and the "session" during which the rights of the displayed article are retrieved and displayed. Generate a key. The bookmarklet also sends any available information about the article to the rights advisor web page 108. The rights advisor web page 108 uses the article information to try and search for rights associated with the article. In addition, in accordance with the principles of the invention, the web server that displays the rights advisor web page also searches the original website from which the displayed article was read to attempt to find additional information about the article. To do.

  The process performed by rights advisor web page 108 to search and determine rights is described with reference to FIG. The process begins at step 500 and proceeds to step 502 where the rights advisor web page 108 receives article information, organization member context, and the type of usage desired from the bookmarklet 104. Rights available to the organization are defined by contracts stored in rights database 112. The rights database 112 is configured as a plurality of tables in which rights are stored in a table different from the content identifier. Such a database is described in US Pat. No. 5,991,876, which is incorporated by reference in its entirety. In particular, the rights database 112 stores information about contracts.

  A contract is any structure that an organization must follow when it acquires or represents a right to secondary use of content. Such a contract could include a copyright license for the entire group of publications acquired from the rights clearinghouse. An example of such a contract is an annual copyright license obtained from the US Copyright Fee Settlement Center. The contract can also be created directly by the publisher, for example, a Pharmaceutical Document Ring contract by the publisher Elsevier. Other types of contracts can be created by other Reproductive Rights Organizations, such as, for example, by the UK's Copyright Licensing Agency, and contracts can also be obtained from various content aggregators. it can. Such a contract has a license from Factiva. Contracts can also be implied by grammar, eg Swiss law allows Swiss companies to share content without loyalty. Yet another contract includes company policy.

  At step 504, rights advisor 108 accesses the rights database as indicated by arrow 114 to retrieve all contracts used for the organization. The components of the contract 600 as represented in the rights database 112 are shown in FIG. These components include scope 602, included title 610, right 620 and condition 621. Scope 602 specifies a member context or various constraints, the organization member must be adapted to be covered by the contract, and is defined by three variables: country, location, and organization Attribute. Country variables have values corresponding to nationalities around the world, such as the United States or France. The location variable has a value corresponding to the location of various locations in the organization, such as the location of Waltham or the location of Wilmington. An organization-defined variable can have any value within an organization that determines whether a contract applies to members of that organization. For example, a variable specifies that an organization member is subject to a contract, such as that it must be a member of a marketing department or a research and development department. The country, location, and organization-defined variables are assigned the value “any” indicating that the contract applies to any member context that matches the other scope variables. For example, the value “any” applies to organization-defined variables, in which case the contract applies to any member that meets the country and location scope variables.

  The contract 600 also includes an indication 610 of the issue or title targeted by the contract 600. The contract 600 can be applied to a collection 612 in which publications are arbitrarily classified. For example, a contract can be applied to all titles included in an EBSCO subscription package. This can be considered a “public” collection, the titles included are defined by the information provider and are the standard for all purchasers of the package. Another approach is a “personal” collection. For example, an organization can create an “à la carte” subscription from a provider such as EBSCO. Contract 600 can also be applied to a separate publication 616 in addition to or instead of collection 612.

  The third component of the contract is a right 620 associated with the contract. Each right is associated with a specific usage type. In order to standardize the contract, a set of distinct rights is predetermined. In the following discussion, a set of distinct usage types is predetermined for a publication. However, as those skilled in the art will appreciate, a set of predetermined rights effectively includes distinct rights. For example, an exemplary set of predetermined rights includes (1) sending a copy of the issue to an organization member by email, and (2) configuring a copy of the issue in the organization. E-mail to non-members, (3) store a copy of the issue on the local hard drive, (4) store a copy of the issue on a shared network drive, (5) issue of the issue Reading a copy and sending it to an organization member by e-mail; (6) Reading a copy of the issue and sending it to a person who is not a member of the organization; (7) Photocopying the issue. (8) Photo-copy the publication and share it with someone who is not a member of the organization. (9) Share a printed copy of the publication with the organization member. (10) Printing (11) Share a copy of the publication using Lotus Notes ™ (12) Copy the publication to an Internet site Uploading, (13) posting a copy of the publication for advertising purposes, and (14) uploading a copy of the publication to electronic paper (soft advertisement). Customers can define their own usage types, but these customer usage types must correspond to one of 14 predetermined usage types.

  Rights can be associated with each usage type. In addition, rights may be specified for the contract 600, as indicated by arrow 622, may be specified for the collection covered by the contract, as indicated by arrow 624, or by arrow 626. As shown schematically, it can be specified for individual publications in the collection. Rights may also be assigned to separate issues that the contract individually targets, as indicated by arrow 628.

  A condition 621 can also be associated with each contract. Conditions include rights holders, restrictions that cannot be expressed in the program as rights, eg specific syntactics such as Swiss law that allow publications to be shared with other Swiss employees, and company policies It is. Conditions can be assigned at the issue, collection and contract level. In general, rights-related conditions are tagged as “restrictive” or “non-restrictive”. The tag “Restrictive” has related rights (such as the right to photocopy publications) restricted by the text of the condition (for example, “Restrictive conditions include“ only internal distribution is possible ”) Indicates. The tag “non-restrictive” indicates that the condition does not limit the applicability of rights, perhaps because the condition expands the range of permitted actions (eg, non-restrictive conditions). "There are no restrictions on distributing photo copies of this content").

  Returning to FIG. 5, at step 506, as indicated by arrow 120, the rights advisor accesses the metadata database 122 and the standard number of the publication that contains the article of rights information requested by the member. Try to take. This is to determine if any retrieved contract is applicable to the issue. In accordance with the principles of the present invention, Rights Advisor attempts to search for publications using two separate methods that are performed in parallel.

  According to the first method, the rights advisor attempts to search for publications using information received from the member's browser. If this information includes the title of the article and an authenticated standard identification number, such as the ISSN number or ISBN number of the issue, only this information could be used to search for the issue. However, in some cases, only the article URL may be available. Article URLs are often given arbitrarily and, as such, provide a consistent meaning for determining whether a given article is published in a publication with an authenticated standard identifier. I don't have it. Accordingly, the rights advisor web page 108 attempts to map or convert the URL to a standard identifier available there. Using this standard identifier, rights advisor web page 108 can access metadata database 122 to obtain a standard number identifying the issue. This standard number can be used for retrieved contracts to allow the organization to determine which contract applies to the specified issue.

  The URL mapping performed by the rights advisor depends on various URL parsers, and each parser uses a parsing algorithm and a support database 118 in URL format. In particular, rights advisor program 108 may separate a set of rules to determine which parsers are available for a particular URL, and a specific URL into a website-specific identifier that is valid for a URL mapping task. Use one possible set of parsers. Once these unique identifiers are obtained, they are applied to a database of rules 118 for converting website-specific identifiers into standard identifiers, such as ISSN or ISBN identifiers, as indicated by arrow 116. Once the standard identifier is obtained, it is applied to the database 112 that is entered with the standard identifier for the issue as indicated by arrow 114. This database 112 lists the titles of publications and the rights to follow when the publications are available.

  An apparatus 700 for obtaining standard identifiers from article information is illustrated in FIG. 7, and the steps of the search process are illustrated in FIGS. 8A and 8B. The search process begins at step 800 and proceeds to step 802 where information 702 about the article displayed there is received from the member's web browser 102. Attempt to search for corresponding issue in metadata table 734 (as indicated by arrow 703) using information such as title or any standard number present in the information received from the browser at step 804 Is performed by the web server. If this attempt is successful, a standard identifier is returned, as indicated by arrow 736, as determined at step 806, processing proceeds via off-page connectors 822 and 828, and ends at step 848.

  If the attempt is not successful, processing proceeds to step 808 where the domain name is saved by the web server using, for example, a store-and-forward dispatcher. This storage operation triggers two processes operating in parallel that attempt to place a standard identifier for the applicable issue. The first process is described in steps 810, 814, 818, 824, 830 and 834. The second process is described in steps 812, 816, 820, 832, 836, 840 and 842.

  In step 810 of the first process, a set of parser rules 704 that determine the most suitable URL parser using the URL of the website being viewed in the member's browser as indicated by arrow 703 Queries as well as configuration settings that determine how the parser is used in the case specified by the rule. In particular, the domain name stored in the URL is matched with the set of parser rules to select a rule that applies to the domain. Next, a parser is selected and configured using the selected rules.

  FIG. 9 shows an exemplary embodiment 900 of a set of parser rules 704. In this embodiment, the set of parser rules is implemented as a set of relational database tables 902, 904, 906, 910 and 912. Each content provider is provided with a record in the content provider table 902 that stores a unique identifier (CONTENT_PROVIDER_ID) and name (CONTENT_PROVIDER_NAME). A content provider can be associated with one or more Internet domains via a content provider domain table 904. Table 904 stores one or more records for each content provider, where each record has a domain identifier (CONTENT_PROVIDER_DOMAIN_ID), a domain name (CONTENT_PROVIDER_DOMAIN), a reference to the content provider (CONTENT_PROVIDER_ID), and multiple domains Stores a priority level (PRECEDENCE_LEVEL) indicating which domain to check first. The table also includes a URL segment map identifier (URL_SEGMENT_MAP_ID) and a URL parser identifier (URL_PARSER_ID) for each domain. The URL segment map identifier specifies a record in the URL segment map table 912 containing data indicating the structure of the URL, which is composed of three segments (URL_SEGMENT_1, URL_SEGMENT_2, and URL_SEGMENT_2). A standard issue number or issue identifier may be directly associated with a domain name. In this case, these identifiers are stored in the URL segment map (STD_NO and PUB_ID).

  If the issue identifier cannot be directly associated with the domain name, the URL parser is associated with the content provider domain via a reference to the URL parser table 906. Table 906 includes a parser identifier (URL_PARSER_ID) and parser name (URL_PARSER_NAME) and an indication of whether a particular parser is valid. A further table 910 (URL parser parameter table) stores parameters used with a particular parser.

  Returning to FIG. 7, after selecting a set of parser rules based on the domain name in the URL, step 814 is performed using one of the set of parsers indicated by parsers 706 and 708 identified by the selected rule. Parses the URL and generates a data field value. The parser consists of instructions for extracting from the URL the data fields necessary to determine the standard identifier using the conversion rules. Such a set of data fields includes three elements: a key base, a periodicals key, and a publication date. The key base specifies the context in which the generated identifier is meaningful. In other words, each publisher can give every publication on the website a unique dedicated number and use this numbering system in the URLs of articles on that website. The key base in this case can be an arbitrary character string such as “PUB1” that specifies the website of the publisher, and the journal key is a dedicated identifier owned by the publisher.

  Parsers such as parsers 706-708 are defined to extract data in a specific format. For example, many publishers follow informal conventions where the URL of an article includes a unique string concatenation that identifies the issue with a four-digit number representing the year and month of publication of the article. Various well-known parsing techniques can be used to find this string and split it into the desired components. When a parser is created and this concatenated string is extracted from the URL and the string is split into two useful components, the parser is composed of parser rules as described above and follows this convention. The same task can be executed for any publisher URL. Any chosen parsing technique must be capable of implementing at least the following functions: That is, a specified prefix character string is searched for within a given character string. Characters following the prefix string are extracted until the specified suffix string is searched. Then, the extracted character string is divided into a plurality of sub character strings according to a simple format specification. These parsing and extraction tasks can be easily performed by conventional UNIX regular expressions or regular expressions such as Perl. In general, new parser rules and parsers can be added to support new URL formats. A more detailed discussion of the parser and its composition can be found in C.I. Howard, J.M. Arbo and V.A. A Method and Apparatus for Converting Document URLs to Standard Document Identifiers and Methods for Converting a Method and Apparatus for Converting a Document Universal Resource Locator to a Standard Document Identifier. 11 / 733,423. This disclosure of the present application is hereby incorporated by reference in its entirety.

  The process then proceeds to step 830 via off-page connectors 818 and 824, and the extracted data field values are provided to the conversion rules database 716 as indicated by arrows 712 and 714. The conversion database includes a plurality of items, and each item constitutes a conversion rule. The conversion rule includes at least three fields, a key base, a journal key, a standard identifier, and other data fields. Field can be included. The key base and journal key are used as key fields. If the data field values provided for the transformation rule database match these fields, the associated standard identifier is returned.

  Since the journal key is internal data of a particular publisher, there is no guarantee that the journal key is unique outside the context of a particular website or subset of websites. Keybase provides a mechanism that ensures that journal keys can be accurately mapped to standard identifiers such as ISSN. If at step 834 it is determined that such a standard identifier is due to a database query, then the URL mapping process proceeds to step 836 where an attempt is made to search for publications using the standard identifier. If an issue is found, as determined at step 840, processing ends at step 848.

  A second process for obtaining a standard identifier for a publication begins at step 812. As described above, this process is started when the domain name is stored (at step 808), and proceeds in parallel with the URL parsing process described above. At step 812, a domain specific script, called a metadata parser, is retrieved from the URL mapping database 118. As an example, the script can be Javascript. As shown in FIG. 9, the metadata parser script is stored in the metadata parser table 908. Each record in this table includes a parser identifier (METADATA_PARSER_ID), a domain key (SELECT_KEY), an indication of whether the script is valid, script text (SCRIPT_TEXT), and a timeout interval and re-execution for script execution. There are several timing entries that control the trial strategy. Each script can also be invalidated for a particular customer by making an entry in the metadata customer invalidation table (METADATA_CUST_DISABLE) 914. Using the URL of the web page as the domain key, access table 914 and retrieve the script text specific to that domain.

  The retrieved script text is downloaded to the member's browser and appended to the bookmarklet script already running in the browser using the timing and number of retries stored with the script. When activated, the script text parses the HTML code of one or more web pages on the current website and uses the timing and retry information stored with the script again to produce the desired publication. Try to find additional data about things. For example, such a script can parse HTML code for a web page that a member is currently viewing. Alternatively, the script can navigate from one page to another web page and parse the HTML code on the second web page. As an example, this can happen in situations where a member is viewing the full text version of an article, but the publication information for that article is available on different web pages that display a summary of the publication.

  Scripts are typically designed by an operator who accesses a website, takes note of the location of additional information, and writes the script to retrieve information. Operators can generate scripts “from scratch” using the site's general workflow to extract content identifiers as a functional limitation, but in most cases, operators will be able to generate existing metadata parsers. Will start with a script. Because scripts designed to process similar types of publications are generally similar in structure, each issue type has a template script that can be modified for a specific domain. For example, template scripts can be used for industry periodicals, news articles, patent publications and press releases, or have similar page layouts and types, or similar metadata can be extracted, or similar site structure Can be designed for other sites with Alternatively, if the content or document being parsed is of similar type and structure, or if it contains the same kind of metadata, such as a copyright notice author name or year, the operator will use an existing script. It can be determined. For example, the copyright notice is displayed at the footer of most web pages, at the bottom of the page. A typical format is “Copyright (c) 2006 copyright holder name”. Because the format and captured data are similar, system users can modify existing scripts to perform the same functions on different websites or sets of pages.

  The template script or existing script can be selected by the operator based on the URL of the website, as schematically illustrated by arrow 719 in FIG. The operator usually logs on to the website with a temporary account, takes note of the location of related information, modifies the template script, and navigates to that location. This modification is performed by applying an existing script to the script editor 721 to generate a new script 723 that is a script stored in the metadata script parser table 720. As an example, the template script for industry periodicals avoids header information and parses the remaining HTML script with the first 1000 of HTML code to parse with a parser similar to that for the URLs discussed above. Bytes can be skipped.

  In general, scripts are site specific. For example, a web page created with HTML code and other format elements requires a different parser than a page coded with PDF (Portable Document Format). However, an identifier such as ISBN (International Standard Book Number (International Standard Book Number)), ISSN (International Standard Serial Number), or DOI (Digital Object Identifier) (such as a digital object identifier) is searched similarly. Pages can be used in many sites and services for a particular type of work (eg, a book, periodicals, or research article).

For example, FIG. 10 is an image of an exemplary web page from publisher Elsevier's website, including ISSN (0304-4203) embedded in web page text identifying the periodicals “Marine Chemistry”. FIG. 11 shows an HTML code for generating the web page display shown in FIG. 10 in a conventional web browser. In order to parse the HTML code shown in FIG. 11, the parser proceeds through DOM (Document Object Model) to select a document identifier (ISSN, DOI, etc.). DOM provides a hierarchical structure of web pages with values, allowing the program to search and step through a fixed form to gather the necessary information. Format consistency is important, but with page information returned by DOM, if the class is equal to, for example, “journalinformation”, for example, query the <span> tag, then regular expression matching, etc. Various conventional methods can be used to extract a standard number from the returned block of text.
The following is an example of a metadata parser script configured in accordance with the principles of the present invention. This script is described in the Javascript language.

  In this example, 1 to 35 lines of code define various variables that are used in later subroutines. The code on lines 36 to 84 defines a subroutine that determines whether the protocol of the web page under examination is http or https. The 85 to 118 lines of code define a subroutine that searches for a text string in search of the occurrence of another text string. The codes on lines 119 to 204 use the search function defined on lines 85 to 118 to sequentially search the web page html code for a predetermined character pattern indicating the presence of the standard identifier of the publication and the title of the document. Search for. Lines 205 to 218 define a subroutine for storing the metadata information retrieved from the html code of the web page in the bookmarklet data storage. The code from line 219 to line 243 displays debug information and leaves the web page intact after a metadata storage operation. The code from line 244 to 251 refreshes the user's display window, and the code from line 252 to 262 executes the parsing subroutine.

  The metadata may not be included on the first displayed web page, but only on the previous page or on the page that requires the user to interact with the website. Thus, some metadata parser scripts can perform the functions necessary to navigate the client browser up and down in the browsing history before extracting the metadata. When creating a script for a new site that needs to control browser search, the user of the system can begin generating a new metadata parser script from an existing metadata parser script that includes this functionality.

  At step 816, the script is executed in the member's browser to parse the HTML code and search for related issue information. This information may include, for example, the issue title and a standard issue number such as an ISSN or ISBN number. Processing then proceeds to step 832 via off-page connectors 820 and 826, where any information extracted from the website is stored using the bookmarklet key as a search key. Information storage is required at this point because the first process is still in progress.

  In step 834, the first process determines that the issue identifier cannot be searched by parsing the issue URL, or the attempt to search for the issue with the identifier arranged in step 840 has failed. If it is determined, the process proceeds to step 838, and it is determined in step 832 whether or not any issue information is stored by accessing the storage with the bookmarklet key described above. If the issue information is not searched, the process proceeds to step 846 where a search web page is displayed, causing the member to perform a manual search for issue information, and the process ends at step 848.

  Alternatively, if it is determined in step 838 that the information acquired and stored by the second process is searched using the bookmarklet key, the information stored in step 842 is used to search for an issue. Is made. Before such a search attempt is made, the information can be pre-processed into a standard format to simplify the search process. For example, specific standard information including HTML tags, spaces, foreign language characters and common items can be deleted. A search attempt is then performed using a standard format. The search attempt itself may proceed in several stages. First, the search process attempts to use any standard issue number and title found to generate a “fingerprint” to search for issues. If the attempt fails, the process simply uses the standard number, paying attention to the alternative ID number. If the issue is still not found, the search process uses only the title and looks for a matching fingerprint.

  If an issue is found as determined at step 844, an issue identifier is returned at step 848. Alternatively, if the issue is not found, as determined at step 844, the search web page described above is displayed, causing the member to perform a manual search for the standard issue identifier, and the process ends at step 848.

  Returning to FIG. 5, if, at step 506, a standard issuance identifier has been obtained using one of the methods described above, processing proceeds to step 508 where the rights advisor web server uses the identifier. And determine all retrieved contracts that apply to the identified issue. At step 510, a determination is made for all contracts that match the member context. This determination examines the scope of each contract and determines whether the contract covers the country and location of which it is an element and whether the members meet the attributes defined by any organization Is done.

  At step 512, the best right among the types of usage required is determined. Then, the process ends at 514.

  The process of determining the best rights, as described in step 512, is applied to the issue and configured to determine the rights most appropriate for the type of use included in the contract. It also involves investigating each contract that fits the employee context. In the execution of this survey, each contract is examined “bottom-up”. That is, more specific rights take precedence over more general rights. Therefore, the contract is first examined to determine whether the rights of the type of use required have been assigned to a directly specified issue, either for itself or for an issue that is included in the collection. If such a right is found, it is the right used for the contract. If no such rights were assigned to the issue, the contract is checked to determine if the type of use right requested has been assigned to the collection containing the specified issue. If assigned, it is the right used for the issue. If no such right is found, the contract is checked to determine if the type of use right has been assigned at the contract level. If so, that right is used for the contract.

  The most applicable rights are then collected from all contracts and ordered. Specifically, rights are placed in order from special best to bad based on the type of rights and whether any conditions are associated with the rights. In order to make a decision, a right having a condition tagged “Nonrestrictive” is treated as an unconditional right, ie, one that is easy to apply at the highest level. The order of rights from best applicability to worst applicability is: (1) the right to use without obtaining relevant conditions, (2) the right to use with relevant restrictive conditions, (3) Rights that can be purchased under pre-approved terms, (4) Rights that are available for purchase, but the rights holder must touch more information, (5) Rights that are available for purchase, but special (6) contact the expert to determine the rights, and (7) no rights available. If the right cannot be determined, it is handled as (6) above.

  After the available rights are gathered and ordered, a determination is made as to whether the ordering has resulted in an “overwhelming winner”. That is, one contract contains more applicable rights than those contained in all other contracts. If an “overwhelming winner” has occurred, this “overwhelming winner” is used to determine the rights and conditions of the type of use required. These rights and conditions are then displayed to members of the rights advisor web page.

  In the absence of an “overwhelming winner”, there is a “link” between two or more contracts. The connection between two or more rights can take several forms. For example, a connection between two or more unconditional rights indicates that the same right can be obtained from two different contracts. Since the rights are the same and cannot be distinguished, one contract is selected by various techniques (eg, arbitrarily) and the rights and conditions of the contract are displayed.

  Alternatively, if there is a connection between two or more conditional rights, then all such rights will be displayed with the condition, so the end user will be informed about the admissibility of the required action. Judgment based on can be made. Another example is a connection between two or more rights that have a “Purchase” status. Such a connection will result in a list of possible purchase information for all such rights. In another embodiment, when an issue is selected, the “best” rights available for the various types of use are determined and presented to the members simultaneously.

  If the rights are displayed on the rights advisor web page, processing ends at step 514.

  The software implementation of the above-described embodiments may be a series of computer instructions fixed to a tangible medium such as a diskette, CD-ROM, ROM, or fixed disk, or a modem or other over a transmission path. A series of computer instructions that can be transmitted to the computer system for storage via the interface device. The transmission line may be a tangible line including but not limited to an optical communication line or an analog communication line, or implemented with wireless technology including but not limited to microwave, infrared, or other transmission technology can do. The transmission line can also be the Internet. The series of computer instructions embodies all or part of the functionality previously described herein with respect to the present invention. Those skilled in the art will appreciate that such computer instructions can be written in a number of programming languages for use in many computer architectures or operating systems. Further, such instructions can be stored using any memory technology, including but not limited to, semiconductor, magnetic, optical, or other memory devices, now or in the future, or optically in the present or future. It can be transmitted using any communication technology including, but not limited to, infrared, microwave, or other transmission technologies. Such computer program products can be distributed as removable media, eg shrink wrap software, with attached printed or electronic documents, eg preloaded in a computer system onto a system ROM or fixed disk It is intended that it can be distributed from a server or an electronic bulletin board over a network such as the Internet or World Wide Web.

  While exemplary embodiments of the present invention have been disclosed, it will be apparent to those skilled in the art that various modifications may be achieved without departing from the spirit and scope of the present invention. Changes and modifications can be made. For example, as will be apparent to those skilled in the art, processing operations different from those shown may be performed in other implementations. Other aspects, such as specific processing flows and exemplary sequence of steps, are intended to be covered by the appended claims, as well as other modifications to the inventive concepts.

Claims (20)

A method for searching for a standard publication identifier that identifies a publication containing an article referenced in a web page of a website displayed in a browser, comprising:
(A) A step of creating a plurality of parser scripts, each of the parser scripts extracting publication information from at least one web page of the website by parsing the HTML code of the web page A step adapted to
(B) selecting one of the parser scripts based on the website domain;
(C) downloading the selected parser script to the browser and executing the downloaded script in the browser;
(D) using the information extracted from the website to access a database storing a standard issue identifier indexed by issue information and determining the standard issue identifier. A method characterized by.   Step (c) uses the parser script to navigate from the web page displayed in the browser to another web page in the website and parse the HTML code of the other web page The method of claim 1, further comprising the step of extracting issue information.   The method of claim 1, wherein step (d) includes the step of formatting the information extracted from the website into a predetermined format and using the information to access the database.   4. The method of claim 3, wherein step (d) includes accessing the database using at least two different combinations of the information. (E) creating a plurality of parser rules, each of the parser rules being adapted to extract publication information of a particular format URL (Universal Resource Locator);
(F) selecting one of the parser rules based on a domain of the website, and parsing the URL of the website with the selected rules to extract publication information;
The method of claim 1, further comprising: (g) obtaining the standard issue identifier using the issue information extracted in step (f).   The method according to claim 5, wherein the step (e) and the step (f) are performed in parallel with the step (b) and the step (c). (H) creating a plurality of conversion rules, each of the conversion rules inputting issue information and outputting a standard issue identifier;
(I) inputting the issue information extracted in step (f), applying the issue information to one of the plurality of conversion rules, and using the output of the conversion rule as the standard issue identifier; When,
The method of claim 5, further comprising:   The method of claim 1, further comprising displaying an issue search web page in a browser if the standard issue identifier cannot be determined in step (d).   The step (a) includes selecting a template script based on the domain of the website, accessing the website, and correcting the template script to obtain the publication information. The method of claim 1.   The method according to claim 1, wherein the publication information includes at least one of a title of the publication and an publication identification number. A device for placing a standard issue identifier that identifies an issue containing an article referenced in a web page of a website displayed in a browser, comprising:
Means for creating a plurality of parser scripts, each of the parser scripts extracting from the at least one web page of the website the issue information by parsing the HTML code of the web page; Means adapted,
Means for selecting one of the parser scripts based on a domain of the website;
Means for downloading the selected parser script to a browser and executing the downloaded script in the browser;
Means for accessing a database storing a standard issue identifier indexed by publication information using information extracted from the website and determining the standard issue identifier;
A device comprising:   Means for executing the downloaded script in the browser using the parser script to navigate from a web page displayed in the browser to another web page in a website; 12. The apparatus according to claim 11, further comprising means for extracting issue information by parsing the HTML code of a page.   The means for accessing a database using information extracted from the website includes means for converting the information extracted from the website into a predetermined format, and means for accessing the database using the information. The apparatus of claim 11, comprising:   14. The means for accessing a database using information extracted from the website includes means for accessing the database using at least two different combinations of the information. apparatus. Means for creating a plurality of parser rules, each of the parser rules being adapted to extract publication information of a particular format URL;
Means for selecting one of the parser rules based on the domain of the website;
Means for parsing the URL of the website with the selected rules to extract publication information;
Means for obtaining the standard issue identifier using the issue information extracted by means for parsing the URL;
The apparatus of claim 11, further comprising:   Means for selecting one of the parser rules based on the domain of the website and means for parsing the URL of the website with the selected rules to extract publication information; Means for selecting one based on the domain of the website and means for downloading the selected parser script to the browser and executing the downloaded script in the browser. The apparatus according to claim 15. Means for creating a plurality of conversion rules, each of the conversion rules being configured to input issue information and output a standard issue identifier;
The publication information extracted by the means for parsing the URL of the website with the selected rule is input, applied to one of the plurality of conversion rules, and the output of the conversion rule is output Means for use as the standard issue identifier;
16. The apparatus of claim 15, further comprising:   If the standard issue identifier cannot be determined by means for accessing the database using the information extracted from the website and determining the standard issue identifier, the issue search web page is displayed on the browser. 12. The apparatus of claim 11, further comprising means for performing.   The means for creating the plurality of parser scripts includes means for selecting a template script based on the domain of the website, and a script editor for correcting the template script to obtain the publication information. The apparatus according to claim 11.   The apparatus according to claim 11, wherein the publication information includes at least one of a title of the publication and the publication identification number.

Images