factiva symbology feed - dow jones guidelines v1.76.doc · web viewnot all users of the company...

Factiva Intelligent Indexing Company Codes Feed: Product Specification and Implementation Guidelines Sept 2002

Factiva Intelligent Indexing – Company Codes Feed

Product Specification & Implementation Guidelines

Synopsis: Factiva provides a continually updated feed of listed and unlisted company information and symbols in XML format under the name: Factiva Intelligent Indexing – Company Codes Feed, herein also referred to as “Company Codes Feed”.

This document describes the content specification, product design and implementation guidelines for this product.

Status: For Release; last updated January 2003

Author: Rob ArnoldContributors: Glenn Fannick

Beth GoldenFrances HockingChris Porter Paul Woodward

Date: 6 January 2003Version: 1.76

This document contains information proprietary to Dow Jones Reuters Business Interactive LLC (known as Factiva) and may not be reproduced, disclosed or used in whole or part without the express written permission of Dow Jones Reuters Business Interactive LLC.

Copyright DJRBI 2003

of 29


Contents

1. Background Information on Factiva Intelligent Indexing Page 3

2. Product Overview Page 3

3. Company Coding Policies Page 43.1 Companies included in the Company Codes Feed3.2 Maintenance Policies and Standards of Service

4. Feed Scope and Content Page 44.1 Data elements provided4.2 Listed and unlisted companies

5. Information format Page 9

6. General XML Design Page 106.1 SymList6.2 SymDoc6.3 Control6.4 Metadata6.5 ReplyItem6.6 Company6.7 Sample File Format

7. Delivery Page 127.1 Full feed7.2 Incremental feed7.3 System architecture7.4 Document Retrieval Methods

7.4.1 FTP (File Transfer Protocol)7.4.2 HTTP (Hypertext Transfer Protocol)

7.5 File Naming Conventions & Directory Structure

8. Pseudo Code for Company Codes Feed File Processing Page 16

APPENDICES

Appendix 1 : Feed Descriptions Page 18

Appendix 2 : XML Schema Information 1

Page 2 of 29


1. Background Information on Factiva Intelligent IndexingFactiva Intelligent Indexing™ is Factiva’s taxonomy, used for the classification and categorization of company and business information.

Our comprehensive Company Codes Feed comprises about 300,000 codes for public (listed) and private (unlisted) companies from around the world. Factiva’s extensive database of company codes, multiple alternative names (aliases), industry and region classifications and additional corporate information is maintained by a dedicated team of content specialists.

2. Product OverviewThe company information described above is made available to customers via the Factiva Intelligent Indexing Company Codes Feed.

Customers and integrators are able to derive extensive value from this company codes data through a range of information integration activities, broadly connected with applying the Factiva taxonomy to internal corporate data and third party information and or/mapping and linking that information to Factiva data .

XML formatted files containing the latest Factiva company code information are made available to Company Codes Feed customers via a Factiva server. The method used for delivery of this information from Factiva to the neutral server is the same as that employed by Factiva Select, Factiva’s XML-based current awareness news feed.

Factiva Select and the Company Codes Feed support file retrieval using one of two standard Internet protocols:

FTP (File Transfer Protocol)and

HTTP (Hypertext Transport Protocol).For either protocol, the user must be authenticated using the user name and password provided by Factiva.

Important note: In order to integrate company information into the client’s environment, development effort will be required for integrating the data into new or existing applications.

Factiva Professional Services technical and editorial staff will be happy to offer assistance when required. For more information on Factiva Professional Services technical and editorial assistance, see http://www.factiva.com/consulting.asp?node=menuElem4.

of 29

http://www.factiva.com/consulting.asp?node=menuElem4


3. Company Coding Policies

3.1 Companies included in the Company Codes FeedFactiva’s policy is to create codes for any companies, quoted or unquoted, that receive a reasonable volume of major news coverage. Factiva’s coding desks around the world contribute to the process of code creation. In a typical month between 600 and a thousand new codes may be created.

Factiva company codes are created for: independent companies, both quoted and unquoted (this includes

50/50 joint ventures, as no single company owns a majority stake in the venture)

quoted subsidiaries a limited number of unquoted subsidiaries a limited number of organisations mutual funds and investment trusts consortia

Standard Factiva practice is that a new code is created whenever a company, or one of its quoted subsidiaries, is the main subject of a news article and there is a reasonable expectation of ongoing news coverage (and no code has previously been created to reference that company).

In addition, Factiva systematically creates company codes for global equity RICs (excluding “pink sheet” companies).

Major newsworthy unquoted subsidiaries can also have codes created for them, if there is reasonable justification for doing so.

3.2 Maintenance Practices and Standards of ServiceFor your guidance, Factiva’s maintenance practice is to act on information received relating to company code changes on the same day wherever possible. For quoted companies, Factiva staff are in continuous contact with Factiva's parent company staff at both Reuters and Dow Jones regarding corporate events. Factiva maintains a network of editorial staff around the world who monitor these changes from news in Factiva's source content; and customer input on corporate changes is also actively encouraged. Factiva also uses natural-language-based entity detection software to further enhance its on-going company name monitoring.

4. Feed Scope and ContentCompany information is split into multiple feeds, meaning there is some flexibility in specifying the exact information which customers receive through the combination of feeds chosen.

Customers can keep their locally hosted information up to date by regularly processing either: a “full” feed (delivering the full set of Factiva codes and company

information), or

of 29


an “incremental” feed (delivering all modifications over a 24-hour period – i.e. additions, amendments and deletions)

More detailed information on the delivery times for the full and incremental feed, plus the file-naming conventions used, is included in Section 7 (Delivery).

The full feed content covers over 300,000 companies. Where customers do not wish to use the full feed for either technical or editorial reasons, there are a variety of ways of identifying smaller subsets of the data. Suggested techniques are: include only active companies (see below, section 4.1.2). Around 40,000

companies have the status of “Inactive” principally because they have been merged or taken over.

include only companies having an autocoding alias (see below, section 4.1.6(ii)). Around 60,000 companies have an autocoding alias. Quoted companies, and unquoted companies which have featured in Factiva news coverage since early 2001, will normally have an autocoding alias.

4.1 Data Elements Provided in the FeedA description of the fields included in the Company Codes Feed is set out in the following section.

4.1.1 Factiva Code (Field Name : fcode) Attribute of Company This will be a unique alphabetic code of between 2 and 6 characters in

length. Each Factiva code represents one company, which may be public or private

Unique codes are assigned to all independent companies, quoted subsidiaries, 50/50 joint ventures, mutual funds and investment trusts, consortia and a controlled list of unquoted subsidiaries which attract significant news coverage on Factiva services or which are difficult to search using free text

Codes usually, but not always, bear some similarity to the company name

Factiva codes are also known as Factiva Data Symbols or FDS Codes

4.1.2 Factiva Code Status (Field Name : codeStatus) Attribute of Company Denotes whether this Factiva code is actively being applied by Factiva

or it is inactive and can only be used for historical searching in Factiva’s archive

Possible values for this field are :-- “A” – for active company codes- “I” – for inactive company codes- “DUP” – for duplicate code entries

4.1.3 Company Type (Field Name : compType)Attribute of Company The structure or purpose of the company The most common classifications are: company, joint venture,

consortium, not-for-profit organisation

of 29


This field will typically be set to CO, indicating that the entry relates to a company.

4.1.4 Listing Status (Field Name : listStatus) Attribute of Company Describes whether a company is listed on a stock exchange or is an

unlisted company

Possible values for this field are :-- “L” – for listed companies- “UL” – for unlisted companies

4.1.5 Company Descriptor (Field Name : Descriptor) The company’s full registered name. This field contains a “clean” version of the company name, and represents the company name in full (minus any Factiva formatting).

4.1.6 AliasesThere are two types of aliases in the Company Codes feed - Lookup Aliases and Autocoding Aliases.

(i) Look-up Alias (Field Name : Alias) Lookup Aliases are created for the purpose of supporting client-side lookup functionality. These aliases exist to help the customer identify the relevant company record for their research. The aliases include:- trading names- alternative company names- divisional names- subsidiary names - brand names (in some instances)

With the exception of quoted and major newsworthy unquoted subsidiaries, the entities described above do not have Factiva codes of their own.

By having a lookup alias linked to the parent entry, a customer searching on that lookup alias can be directed to the relevant parent entry.

Depending on client-site implementation, it would also be possible to provide facilities to add a lookup alias as a free-text search in combination with the relevant Factiva company code.

(ii) Autocoding Alias (Field Name : AutoAlias)Autocoding aliases are used by Factiva's autocoding systems, and could also be used for client-side autocoding.

Autocoding systems automatically apply codes to articles by scanning the article's text and identifying various text strings as companies; these text strings are then compared to the autocoding aliases that Factiva holds. Where a text string matches an autocoding alias, the autocoding system will apply the appropriate company code to the article.

The criteria for creating autocoding aliases are much stricter than the criteria for creating lookup aliases.

of 29


If the same lookup alias belongs to two different companies, both entries can be returned via lookup and the customer can decide which company is the relevant one. Autocoding aliases have to be unique.

In addition, autocoding aliases cannot be based on commonly-used words, since this could cause data processing difficulties.

Example: 'Next' would be an acceptable lookup alias for the company Next Plc, but unacceptable as an autocoding alias (since the numerous occurances of the word 'next' would result in excessive and inappropriate application of the code for Next Plc on articles).

4.1.7 LocationCompany location information is split into two categories : country and state code (where applicable).

(i) Country (Field Name : Location fcode)

The country code attached to a company entry reflects the country of registration. A company with headquarters in Belgium and which is registered in Belgium will be assigned the location fcode “Belg” (Belgium), whereas a company with headquarters in Belgium but which is registered in Bermuda will be assigned a location code “Berm” (Bermuda).

Location type = “CNTRY“ indicates that the location is a country.

(ii) U.S. State (Field Name : Location fcode)

U.S. state or Canadian province where a company ‘s headquarters are located, if the company’s country is U.S. or Canada

Location type = “STP“ indicates that the location is a U.S. State or Canadian province.

4.1.8 Company Industry Some Factiva company codes are mapped to Factiva industry codes and/or news subject codes. Companies may be mapped to one or more industry codes which reflect the company’s core areas of activity. These activities are defined as those which generate the most revenue for the company.

Industry codesIndustry codes are alpha-numeric and are between 2 and 10 characters in length. As a general rule, each industry code starts with the letter i. Industry codes are identifiable based on the tag <Industry fcode=i123>

News Subject CodesNews subject codes are alpha-numeric and in general are between 3 and 7 characters in length. As a general rule, each industry code starts with the letter i. Industry codes are identifiable based on the tag <NewsSubject fcode=ABCDEF>

of 29


The list of Factiva Industry and News Subject codes can be found via a link on the Factiva.com public Web site at http://www.factiva.com/content/intindexing.asp?node=left-side-menu2 or downloaded as a structured XML file.

(i) Primary Industry (Field Name : Industry fcode)The industry from which a company’s most significant revenue is derived. Only a single Primary industry code can be provided for a given company.

Industry primary = “T“ indicates that this is the Primary industry code.

(ii) Secondary Industry (Field Name : Industry fcode)Other industries from which the company derives signficant revenue. Multiple Secondary industry codes may apply for a given company.

Industry primary = “F“ indicates that this is the Secondary industry code.

4.1.9 Company Parent InformationFactiva Company Codes for any relevant parent companies are included in the feed. Information will be included on both Immediate Parent (IPA) and ultimate parent companies, as appropriate.

Example: If Company A is a subsidiary of Company B, itself a subsidiary of Company C, then A’s Immediate Parent would be Company B and its Ultimate Parent would be Company C.

An independent company does not have parents so there will be no parent field data present.Both quoted subsidiaries and unquoted subsidiaries will be assigned one or more parent company codes.

(i) Immediate Parent (Field name : Parent fcode) Company owning more than 50% of this company

Parent type = “I“ indicates that this is the immediate parent company.

(ii) Ultimate Parent (Field name : Parent fcode) The company at the highest level of ownership, if this company’s parent is owned by another company

Parent type = “U“ indicates that this is the ultimate parent company.

4.1.10 DJ Ticker (Field name : Code)Tickers are Dow Jones codes relating to traded financial instrumentsThe Ticker itself is contained within the Value field adjacent to Code Type = ‘DJ’

Some tickers just comprise a company identifierExample: RTRSY is the ticker for Reuters Some tickers comprise a company identifier plus a country identifier.

Example: G.VOW is the ticker for Volkswagen. G indicates that the company is traded on a German exchange.

of 29

http://www.factiva.com/content/intindexing.asp?node=left-side-menu2

http://www.factiva.com/content/intindexing.asp?node=left-side-menu2


Note: A small number of tickers exist for private companies which do not trade on any exchange. These can be identified by the prefix “X”.

Code Type = ‘DJ’ indicates that the company is linked to a Dow Jones Ticker.

Use of DJ Ticker is subject to license conditions which are set out in your contract. Not all users of the company codes feed will be eligible to use DJ Ticker.

4.1.11 Reuters Instrument Codes – RICs (Field name : Code) RICs relate to traded financial instruments (shares, ADRs, etc). Factiva provides mappings to global equity RICs (excluding “pink sheet” companies).

The RIC itself is contained within the Value field adjacent to Code Type = ‘RIC’

The main RIC components are:- the company identifier - the exchange identifier

Example: RTR.L is the RIC for Reuters trading on the London Stock Exchange.RTR is the company identifier for Reuters and L is the exchange identifier for London.RTR.MU is the RIC for Reuters trading on the Munich Exchange.

N.B. A very small number of RICs exist for companies which do not trade on any exchange. These can be identified by the “exchange” identifier “UL” (unquoted).

The main RIC (preferred or primary RIC) will be marked primary = T. The primary RIC most commonly reflects equity trading on the company’s home exchange.

Code Type = ‘RIC’ indicates that the company is linked to RIC codes.

of 29


RICs in the Company Codes Feed There is a “Core+RICs” company feed available, which includes

Reuters Instrument Codes (RICs). Use of Reuters RIC code is subject to license conditions which are

set out in the contract. Not all users of the company codes feed will be eligible to use Reuters RIC. Users of Factiva services may only use RIC to retrieve data from Reuters and Factiva services, not to retrieve any other internal or external data.

4.1.12 D&B D-U-N-S® (Field name : Code) D&B has the largest company database available, with information on 70 million companies worldwide. Factiva has built a mapping between D&B D-U-N-S® numbers and Factiva company codes, enabling seamless automatic integration of information based on the two identifiers.

D&B D-U-N-S® codes relate to corporate entities. Factiva provides mappings wherever an equivalent Factiva company code exists and there is sufficient data to be confident of a match. Over 90,000 Factiva codes are matched to D-U-N-S®.

The D-U-N-S® is a nine-digit numeric code – e.g. "235660086" is the D-U-N-S® for Anglo American Corporation.

The mapping to Factiva code is one-to-one, with the Factiva code mapped to its direct D-U-N-S® equivalent, most usually a headquarters address.

D-U-N-S® numbers will often exist for units of companies which do not have a direct Factiva company code equivalent – for instance, national and regional branches of an international company – as those units do not meet the Factiva company code creation policy described above in section 3.1. Factiva does not carry mappings for all these lower-level D-U-N-S® numbers. Users are advised to use information from D&B to “walk the tree” of D-U-N-S® number parent relationships up to the level where a mapping to a Factiva company code exists. Initially mappings will be updated once a month.

D-U-N-S® in the Company Codes Feed D-U-N-S® numbers are included in “mapping files”, which contain the

unique Factiva Company Code in conjunction with the unique D-U-N-S® number. By processing this information, the relationship between Factiva Company Codes and the corresponding D-U-N-S® number can be established and maintained

The D-U-N-S® itself is contained within the Value field adjacent to Code Type = ‘DUNS’, and is housed withing the Company and ReplyItem containers in the XML file. (Further information on the General XML design is available in section 6)

Sample D-U-N-S® data as represented in a D-U-N-S® Mapping file :-

<ReplyItem><Company fcode="CAJESP">

<Code type="DUNS" value="466093507" /> </Company>

</ReplyItem>

of 29


Important NoteUse of D-U-N-S® is subject to license conditions which are set out in the contract. Subscribers to Factiva services may use the mappings in their internal data integration environments (including intranets and customer relationship management systems) for the purposes of linking from Factiva codes to D-U-N-S® and D-U-N-S® to Factiva codes, in order to facilitate the integration of D&B information, Factiva information and other information on the client’s internal systems. Not all users of the company codes feed will be eligible to use D-U-N-S®. Mapping files are available for download from the symbology_map

directory; further information on exact file names plus the file directory structure is contained in section 7.5

4.1.13 Company Note (Field name : Note)Comments or details about a company’s recent history, such as mergers, delistings, etc.

The data elements described above are included in the “core” feeds -- Full company feed and Incremental company feed. The Incremental feed includes additional data to describe whether any company record has been added, changed or deleted:-

Action - This will have one of three values - “add”, “del” or “rep” – corresponding to the company record being a new addition, deletion or replacement of an existing record.

Note: The Action data element is also included in the Full feed, but will always contain the value “add”.

4.2 Listed and unlisted companiesFeeds containing listed and unlisted companies are provided separately, allowing the option to process or store data on these two groups of companies separately.

Note: When a company previously found in the unlisted feed becomes listed on a stock exchange, it is deleted from the unlisted feed and added to the listed feed. The reverse happens when a company is de-listed.

5. Information FormatInformation is delivered in XML (SymDoc) format.

XML can be readily integrated into a large number of client applications and environments. For assistance with content integration, you can contract with Factiva Professional Services – a team of technical and editorial experts who have helped clients around the world build and create custom applications using Factiva content and services.

More detailed XML schema information is provided in Section 5 A breakdown for individual feeds is appended

of 29


6. General XML DesignThe general design of the XML files is as a container, that contains further containers. The hierarchy of these containers is as follows:-

<SymList><SymDoc>

<Control></Control><Metadata></Metadata><ReplyItem>

<Company></Company>

</ReplyItem></SymDoc>

</SymList>

The significance and attributes of each of the six containers is described below.

6.1 SymListEach complete Company Codes file is a SymList container, containing one or more SymDoc containers, which contain Company containers (one per company).

The SymList tag has attributes which indicate whether the file is:-(1) an Incremental file (type=”I”) or a Full file (type=”F”). (2) a code corresponding to the file format (e.g. “$CO03” to represent

unlisted core file with RICs) (3) sequencing information, which is required for customers’ scheduling of

file processing

6.2 SymDoc Each SymDoc container describes a single company record The SymDoc container contains one Control container, one Metadata

container and one ReplyItem container.

The SymDoc tag has attributes which indicate:-(1) the action required (which will vary for Incremental files only). For

Incremental files, the values “add”, “del” or “rep” correspond to the company record being a new addition, deletion or replacement of an existing record; for the Full feed this field will always contain the value “add”

(2) the XML version number (currently 01.1)(3) a unique alpha-numeric identifier for the company record

6.3 ControlThe Control container contains feed management and audit information, including the date and time of production.

6.4 MetadataThe Metadata container contains data audit information.

6.5 ReplyItemThe ReplyItem container contains one Company container.

of 29


6.6 Company Each Company container contains the company information, such as FDS code (Factiva Data Symbol), Company name, aliases, RICs, activity codes, and ownership.

A full description of relationships between all key data elements contained within the SymDoc is appended (please refer to Appendix 2).

6.7 Sample File FormatThe following is a sample section from the $CO03 feed "unlisted core with RICs".

of 29


7. DeliveryCompany Codes Feed information in XML format is pulled by the client from a Factiva server, following a daily or weekly schedule. Regular updates for both the Full feed and an Incremental feed are available for download, as detailed below.

7.1 Full feedThe full feed should be used to: deliver a complete set of codes for initial loading into your application bring a database up to date if incremental files have not been pulled

for more than seven days.

A snapshot of the latest Company Code information is taken at 12 p.m. ET (5 p.m. GMT) once weekly, on each Sunday. This information will take several hours to be transferred to the neutral Factiva Select server, after which time it will be available for download by the client.

Factiva recommends that weekly files are scheduled for download by clients no earlier than 5 p.m. ET (10 p.m. GMT) each Sunday.

Each Full feed file contains no more than 1,000 records, in order that they may be processed by certain XML parsers more easily (e.g. DOM parsers). Therefore, there are hundreds of files comprising the largest feed.

7.2 Incremental FeedThe Incremental feed provides daily updates to the full content set, including the addition of new codes and changes to and deletions of existing codes.

Other information about the Incremental feed:(1) Incremental files will be generated by Factiva once every day (seven

days a week) at 12 p.m. ET (5 p.m. GMT), and subsequently transferred to the neutral Factiva Select server.

(2) Factiva recommends that incremental files are scheduled for download by clients no earlier than 1 p.m. ET (6 p.m. GMT) each day.

(3) Each change to an existing company record will generate a full version of the company record, so that no procedure is needed by the client for parsing a partial record.

(4) Incremental feed files will be available for retrieval for a rolling seven-day period, so missed updates can be pulled by the client as infrequently as once weekly.

(5) If the elapsed period between updates exceeds one week, then a Full feed should be pulled to refresh the company record set.

(6) If there are no changes needed for a given day, a “null” file will be created; this provides a record that no changes were made that day. (This would rarely happen on a business day.)

(7) Incremental feed files consist of no more than 1,000 records (and more likely only one file a day for each feed containing approximately a few dozen records), in order that they may be processed by certain XML parsers more easily (e.g. DOM parsers)

(8) In processing multiple Incremental feeds, clients should be aware that records deleted from one feed may be added to another (e.g. when a company is listed it is deleted from the unlisted feed and added to the

of 29


listed feed); this may have timing implications for updating the client’s local Company Codes Feed data

of 29


7.3 System architectureThe architecture and process used for symbology data delivery is that used for Factiva Select, our customisable, current awareness news feed.

7.4 Document Retrieval MethodsTo pull the XML-based Company Code Feed from the Factiva Select server into your corporate environment, you must use one of these standardised Internet protocols:

FTP (File Transfer Protocol) HTTP (Hypertext Transport Protocol)

Note: For either protocol, authentication must be provided using the user name and password given to you by your Factiva representative.

7.4.1 FTP (File Transfer Protocol)To retrieve documents using FTP, follow these steps:

1. Connect to the Factiva Select server.If connecting through a proxy server, you must make sure that the appropriate credentials are passed to the Factiva Select server.

2. Authenticate your identity to the Factiva Select server by using the supplied user name and password.

3. Change to the appropriate directory, using either cd /symbology_MAPor cd /symbology_CORE

A description of the file naming convention and directory structure used is included in Section 7.5 - File Naming Conventions and Directory Structure.

4. Obtain a list of available files (FTP command NLST).

of 29


5. Locate the file(s) which are to be processed based on the file name (which contains sequencing information).

7. For each file requiring download, complete the following:

(a) Retrieve the available file from the Select server (FTP command RETR)(b) Process the retrieved file

Note: If there are difficulties with retrieving or processing a file—say, for example, there is a transient problem inserting the document in your database—repeat this step in its entirety.

7. Disconnect from the Factiva Select server.

7.4.2 HTTP (Hypertext Transfer Protocol)Factiva Select permits the retrieval of the feed via HTTP (Hypertext Transfer Protocol), and provides the URLs described below to augment the basic HTTP functions.

filelistDepending on whether files reside in the /symbology_CORE or /symbology_MAP directory, the URL used will be either http://select.factiva.com/symbology_CORE/filelist.aspor http://select.factiva.com/symbology_MAP/file list.asp

A description of the file naming convention used is included in Section 7.5 - File Naming Conventions and Directory Structure.

Note: No user argument is needed on the URL, but the user will be prompted for their HTTP authentication credentials.

Additional filelist informationThe default listing of the filelist.asp is to display the current files. The user can request a list of the previous files or all the files by using the optional 'files’ argument.

Files is an optional parameter:files = where current (the default) is for the most recent set of files, i.e. today’s files, previous is for the previous day’s files and all is for seven days of incremental files.

For example, to view the previous list of core Company Codes Feed files: http://select.factiva.com/symbology_CORE/filelist.asp?files=previous

File RetrievalTo retrieve files using HTTP, follow these steps:

1. Use the filelist URL (as described above) to obtain a list of available files. If there are currently no available files, simply “sleep” until the next scheduled interval and then repeat this step.

of 29

http://selecdt.factiva.com/symbology_MAP/filelist.asp

http://select.factiva.com/symbology_CORE/filelist.asp


2. Locate the file(s) which are to be processed based on the file name (which contains sequencing information). For each file requiring download, complete the following:

(a) Retrieve the available file from the Select server using one of the following URLs (depending on the directory where the file resides):-

http://select.factiva.com/symbology_CORE/{filename } or http://select.factiva.com/symbology_MAP/{filename }

(b) Process the retrieved file.

Note: If there are difficulties with retrieving or processing files—say, for example, there is a transient problem inserting the file in your database—repeat this step in its entirety.

3. Repeat steps 2(a) and (b) for each file to be downloaded.

7.5 File Naming Convention and Directory StructureData files are made available for download in zipped (.zip) format in two different directories on the Factiva Select server.

The two directories are named \symbology_core and \symbology_map

Based on the files for which you are permissioned, you will have access to one or both of these directories:-

All Company Codes Feed customers will be permissioned to download Core files, which are located in the \symbology_core directory

Customers can additionally be permissioned for the \symbology_map directory, which contains Core+RICs files, plus other permissionable files (including D-U-N-S® mapping files) as these are made available.

The file name format and location is as follows, where ? characters represent the file’s sequence number:-

7.5.1 “Full feed” files\symbology_core\ F_$CO01WDZ_????????.zip – Unlisted Core file \symbology_core\ F_$CO02WDZ_????????.zip – Listed Core file

\symbology_map\ F_$CO03WDZ_????????.zip – Unlisted Core file with RICs \symbology_map\ F_$CO04WDZ_????????.zip – Listed Core file with RICs

\symbology_map\ F_$CO07WDZ_????????.zip – D-U-N-S® mapping file (unlisted companies) \symbology_map\ F_$CO08WDZ_????????.zip – D-U-N-S® mapping file (listed companies)

7.5.2 “Incremental feed” files\symbology_core\ I_$CO01WDZ_????????.zip – Unlisted Core file \symbology_core\ I_$CO02WDZ_????????.zip – Listed Core file

of 29

http://select.factiva.com/symbology_CORE/%7Bfilename%3E

http://select.factiva.com/symbology_CORE/%7Bfilename%3E


\symbology_map\ I_$CO03WDZ_????????.zip – Unlisted Core file with RICs \symbology_map\ I_$CO04WDZ_????????.zip – Listed Core file with RICs

\symbology_map\ I_$CO07WDZ_????????.zip – D-U-N-S® mapping file (unlisted companies)\symbology_map\ I_$CO08WDZ_????????.zip – D-U-N-S® mapping file (listed companies)

8. Pseudo Code for Company Code File Processing The following pseudo code is included to provide guidance on the steps involved in processing (1) a Full Company Codes Feed, or (2) an Incremental Company Codes Feed.

These examples refer to downloads using FTP; the same steps would also apply if using HTTP.

8.1 Full Feed Processing

ftp.login(hostname, username, password)ftp.chdir(directory)ftp.list(directory)

mget_last_available_file(”F_”+feedtype+”???_?????????.zip”)// where feedtype is $CO01, $CO02, etc

Lastsequenceno=downloaded_file_sequence_no// which are the last nine digits in the name stem

for_each_chunk_file_in_zip_file{

// each chunk filename has a 3 digit chunk number appendedread_each_file_in_name_sequencefor_each_SymDoc_in_SymList{

// full feed should contain only addsadd_or_replace_document_by_SymDoc_an_or_Company_fcode

}}ftp.logout

8.2 Incremental Feed Processing

// if this is the first time then use lastsequence-no from full feed

ftp.login(hostname, username, password)ftp.chdir(directory)ftp.list(directory)

while_there_are_more_zip_files{

mget_next_available_file(”I_”+feedtype+”???_+”lastsequenceno+”.zip”)// where feedtype is $CO01, $CO02, etc

lastsequenceno=downloaded_file_sequence_no

of 29


// which are the last nine digits in the name stem

for_each_chunk_file_in_zip_file{

// each chunk filename has a 3 digit chunk numberif_chunk_number_is_END

break_out_of_for // this is the null fileread_each_file_in_name_sequencefor_each_SymDoc_in_SymList{

read_SymDoc_actionif_action_del

delete_document_by_SymDoc_anif_action_add_or_rep

add_or_replace_document_by_SymDoc_an_or_Company_fcode

}}

}ftp.logout

of 29


APPENDICES

Appendix 1 : Feed Descriptions

A1.1 Company “core” feed – Unlisted ($CO01) and Listed ($CO02)

(a)XML Format / Fields Note: The superscript numbers below – e.g. (1) – are used only for cross-referencing to the Fields and Attributes table which follows.

<Company fcode=”FCODE”(1) codeStatus=”CS” (2) compType=”CT” (3)

listStatus=”LS” (4)><Descriptor>DE(5)</Descriptor><Alias>AL(6)</Alias><Location fcode=”RE(CNTRY)”(7) type=”CNTRY”/><Location fcode=”RE(STP)”(8) type=”STP”/><Industry fcode="PIN"(9) primary="T"/><Industry fcode="SIN"(10) primary="F"/><Parent fcode="IPA"(11) type="I"/><Parent fcode="UPA"(12) type="U"/><Code type="DJ" value="DJ"(13)/><Note>NOTE(14)</Note></Company>

of 29


(b) Field Attributes and DescriptionsNote : For ‘unrestricted’ fields, Factiva systems do not limit the size of a field; for this reason, field lengths are approximate and represent good practice only.

Ref

Field Name

Description

Mul

tipl

e? Re

quir

ed? Re

stri

cted

?

Field length

(1) Factiva code.

Attribute of Company tag. A unique alphabetic symbol assigned by Factiva to all publicly traded companies and many private ones that meet certain criteria

NO YES NO 2-6 (alpha)

(2) Code Status Whether this Factiva code is actively being applied by Factiva or it is inactive and can only be used for historical searching in Factiva archives

NO YES YES 1-3 (alpha)Values: A / I / DUP

(3) Company Type

The structure or purpose of the company. The most common classifications are: Company, Joint Venture, Consortium, Not-for-Profit Organisation


(4) Listing Status

Whether a company is listed on a stock exchange or is an unlisted company

NO YES YES 1-2 (alpha)Values: L / UL

(5) Descriptor – company name

The company’s full registered name NO YES NO Up to 100

(6) Lookup Alias Multiple variants of the company name, including alias names, trade names, subsidiary and divisional names

YES NO NO Up to 100

(7) Auto Alias Multiple variants of the company name – suitable for automated application of company codes to a particular article

YES NO NO Up to 100

(8) Region (Country)

Country of the company’s registration NO YES NO Up to 7 (alpha)

(9) Region (State)


NO NO NO Up to 4 (alpha)

(10)

Primary Industry

The industry from which a company’s most significant revenue is derived

NO NO NO Up to 10 (alphanumeric)

(11)

Secondary Industry

Other industries from which the company derives significant revenue

YES NO NO Up to 10 (alphanumeric)

(12)

Immediate Parent

Company owning more than 50% of this company

YES NO NO 2-6 (alpha)

(13)

Ultimate Parent

The company at the highest level of ownership, if this company’s parent is owned by another company


(14)

DJ Ticker The company’s U.S. stock symbols, when applicable

YES NO NO 1-12

(15)

Company Note

Comments or details about a company’s recent history, such as mergers, deli stings, etc.

NO NO NO Up to 1,000

of 29


A1.2 Company “Core with RICs” feed – Unlisted ($CO03) and Listed ($CO04)

(a) XML Format / FieldsNote: The superscript numbers below – e.g. (1) – are used only for cross-referencing to the Fields and Attributes table which follows.

<Company fcode=”FCODE”(1) codeStatus=”CS” (2) compType=”CT” (3)

listStatus=”LS” (4)><Descriptor>DE(5)</Descriptor><Alias>AL(6)</Alias><Location fcode=”RE(CNTRY)” (7) type=”CNTRY”/><Location fcode=”RE(STP)”(8) type=”STP”/><Industry fcode="PIN"(9) primary="T"/><Industry fcode="SIN"(10) primary="F"/><Parent fcode="IPA"(11) type="I"/><Parent fcode="UPA"(12) type="U"/><Code type="DJ" value="DJ"(13)/><Code type="RIC" value="RIC"(14)/><Note>NOTE(15)</Note></Company>

of 29


(b) Field Attributes and DescriptionsNote : For ‘unrestricted’ fields, Factiva systems do not limit the size of a field; for this reason, field lengths are approximate and represent good practice only.

Ref

Field Name

Description

Mul

tipl

e? Re

quir

ed? Re

stri

cted

?

Field length

(1) Factiva code A unique alphabetic symbol assigned by Factiva to all publicly traded companies and many private ones that meet certain criteria


(2) Code Status Whether this Factiva code is actively being applied by Factiva or it is inactive and can only be used for historical searching in Factiva archives

NO YES YES 1-3 (alpha)Values: A / I / DUP

(3) Company Type

The structure or purpose of the company. The most common classifications are: Company, Joint Venture, Consortium, Not-for-Profit Organisation


(4) Listing Status

Whether a company is listed on a stock exchange or is an unlisted company

NO YES YES 1-2 (alpha)Values: L / UL

(5) Descriptor – company name

The company’s full registered name NO YES NO Up to 100

(6) Lookup Alias Multiple variants of the company name, including alias names, trade names, subsidiary and divisional names

YES NO NO Up to 100

(7) Auto Alias Multiple variants of the company name – suitable for automated application of company codes to a particular article

YES NO NO Up to 100

(8) Region (Country)

Country of the company’s registration NO YES NO Up to 7 (alpha)

(9) Region (State)


NO NO NO Up to 4 (alpha)

(10)

Primary Industry

The industry from which a company’s most significant revenue is derived

NO NO NO Up to 10 (alphanumeric)

(11)

Secondary Industry

Other industries from which the company derives significant revenue

YES NO NO Up to 10 (alphanumeric)

(12)

Immediate Parent

Company owning more than 50% of this company


(13)

Ultimate Parent

The company at the highest level of ownership, if this company’s parent is owned by another company


(14)

DJ Ticker The company’s U.S. stock symbols, when applicable

YES NO NO 1-12

(15)

RIC The company’s equity Reuters Instrument Code(s), where applicable

NO NO NO 1-12 (case-sensitive)

(16)

Company Note

Comments or details about a company’s recent history, such as mergers, deli stings, etc.

NO NO NO Up to 1,000

of 29


Appendix 2 : XML Schema Information for Data Elements contained in the SymList and SymDoc

#1 Element name

AccessionNo

Definition unique tokenised identifier for the SymDoc documentElement used by

DocData

Attributes Name Type Usefid xs: string Requiredindex xs: string Required

#2 Element name

AddDate

Definition The date the document was first added to Symbology Element used by

DocData

Attributes Name Type Usefid xs: string Requiredindex xs: string Optionalvalue xs:string Required

#3 Element name

AddTime

Definition The time the document was first added to Symbology Element used by

DocData


#4 Element name

Category

Definition Symbology category of the symdocElement used by

DocData

Attributes Name Type Usefid xs: string RequiredValue xs:string Required

#5 Element name

CodeSets

Definition The CodeSets tag contains codings for internal use onlyElement used by

Metadata

Children CsetAttributes Name Type Use

Index xs: string RequiredPrefix xs: string Required

of 29


Diagram

#6 Element name

Control

Definition Container for feed audit informationElement used by

SymDoc

Children StampDiagram

#7 Element name

DocData

Definition Container for audit and management information about the symdoc document

Element used by

Metadata

Children DocType Category AccessionNo AddDate AddTime ModDate ModTime

Attributes Name Type Useindex fs:string Requiredprefix fs:string Required

of 29


Diagram

#8 Element name

DocType

Definition Document format typeElement used by

DocData

Attributes Name Type Usefid xs: string Requiredvalue xs:string Required

#9 Element name

Metadata

Definition Metadata is the outer container for audit information. It may also contain coding information for internal use

Element used by

SymDoc

Children DocData CodeSetsDiagram

#10 Element ModDate

of 29


nameDefinition The date the document was last modified or replaced.Element used by

DocData


#11 Element name

ModTime

Definition The time the document was last modified or replacedElement used by

DocData


#12 Element name

ReplyItem

Definition ReplyItem is the container for the Symbology Document object

Element used by

SymDoc

Children Company Location NewsSubject Industry InstrumentAttributes Name Type UseDiagram

#13 Element name

Stamp

Definition Stamp allows Distribution and Symbology systems to enter audit information about the path this document took through those systems

Element used by

Control

Attributes Name Type Usetype xs: string Required

of 29


date xs: string Requiredtime xs: string Optionalvalue xs: string Optional

#14 Element name

SymDoc

Definition SymDoc contains all the data for a single Symbology object

Element used by

SymList

Children Control Metadata IndexDoc ReplyItemAttributes Name Type Use

action xs: string Requiredan xs: string Requiredsymdocver xs: string Required

Diagram

#15 Element name

SymList

Definition Outer container for SymDoc Symbology documents Children SymDocAttributes Name Type Use

chunk xs: string Optionalformat xs: string Optionalseqno xs:unsignedInt Optionaltype xs: string Optional

Diagram

of 29

factiva symbology feed - dow jones guidelines v1.76.doc · web viewnot all users of the company...

Documents