| A | B | D | E | F | K | L | M | N | |
|---|---|---|---|---|---|---|---|---|---|
1 | Priority | Standardized Field (color = completed) | Standardized Value (color = completed) | Notes | Source field (proc_Publication_Request.xlsx ) | Action [0=pull, 1=parse, 2=compute, 3=hardcode] | Computation Method/Tools & Frameworks | Responsible | |
2 | Notice Skeleton | ||||||||
3 | 1 | noticeId | 71352 | Request Id | 0 | ||||
4 | 1 | noticeTypeCode | 1 | Type of Solicitation Notice code [RR] | TypeOfNotice | 0 | |||
5 | 1 | noticeTypeName | Notice | Public Hearing, Property Dispositions, Court Notices, Rules, Solicitation, Award, Solicitation, Intent to Award [RT] | Descr [proc_Type_of_Notice.csv] | 0 | |||
6 | 1 | [??] | sectionName | Public Hearings and Meetings | Type of Solicitation Notice [RT] [PD]. Can this be substituted by the type of notice field? | SectionName | 0 | ||
7 | 1 | noticeTitle | 420 LEXINGTON AVENUE OFFICE SPACE | ShortTitle | 0 | ||||
8 | noticeDescription | Bid documents are available Monday through Friday, 9:00 a.m. to 4:00 p.m., for a $25.00 fee in the form of a money order or certified check made payable to NYCHA. Documents can also be obtained by registering with I-supplier and downloading documents. | AdditionalDescription | 0 | |||||
11 | 1 | [??] | otherInfo | The services cannot be timely procured through competitive sealed bidding or competitive sealed proposals. DoITT is utilizing the Negotiated Acquisition Extension procurement source method to provide the services in order to continue to provide uninterrupted service. | Are these only procurement related fields? | OtherInfo [procPublicationRequestDMSSPortal Oct-Dec 2014.csv] | 0 | ||
12 | 1 | [??] | printOut | CITRIX XENAPP ENTERPRISE SOFTWARE SUPPORT SERVICES - Intergovernmental Purchase / Judgment required - PIN# 069141106001 - AMT: $138,375.00 - TO: Citrix Systems, Inc. 851 West Cypress Creek Road, Fort Lauderdale, Fl 33309 Term: 7/1/2013-6/30/2014 - E-PIN: 09613O0019001 | Are these only procurement related fields? | Printout [procPublicationRequestDMSSPortal Oct-Dec 2014.csv] | 0 | ||
13 | Organization | identifier | 841 | AgencyCode | 0 | ||||
14 | name | Department of Transportation | AgencyName | 0 | |||||
15 | classification | Agency | [Manually choose agency] | 3 | |||||
16 | identifier | 141 | AgencyDivisionID | 0 | |||||
17 | parentOrganization | 841 | AgencyCode [AgencyDivision.csv] | 0 | |||||
18 | name | Traffic and Planning | DivisionName [AgencyDivision.csv] | 0 | |||||
19 | classification | Agency Division | [Manually choose agency division] | 3 | |||||
20 | 0 | [DCAS] Agency Abbreviation | NCB | AgencyAbbreviation | 0 | ||||
21 | 0 | [??] | noticeDate | Date / TIME | This needs to be located? How is this different from ad start date? | NULL | 0 | ||
22 | 1 | noticeStartDate | DATE | Start Date | 0 | ||||
23 | 1 | noticeEndDate | DATE | End Date | 0 | ||||
24 | |||||||||
25 | Notice Skeleton Attributes [Stored in separate tables] | ||||||||
26 | 1 | Notice Items [M] | noticeItem | 2, 7, 89 | Proposal: Extraction of notice items when present. Sometimes there are clear demarcations of items (e.g. "In the matter of"...), and sometimes there are not. If there are no separate items, the whole noticeDescription is treated as the item. | NULL | 1 | ||
27 | 1 | itemDescription | #2 IN THE MATTER OF a proposed revocable consent authorizing 140 West Street Condominium to construct, maintain and use a flood mitigation system components in the south sidewalk of Barclay Street, between West and Washington Streets, and in the west sidewalk of Washington Street, between Barclay and Vesey Streets, in the Borough of Manhattan.... | AdditionalDescription | 1 | ||||
28 | 1 | ItemObject | a flood mitigation system | Proposal: [RT] Identifies the details of the item, e.g. a flood mitigation system, a rehabilitation center, etc. For description, please see https://docs.google.com/document/d/1Jr-1DHzdHP0rH77F_Kl8q5HfvJvWiKrFRQwZgZvD3LE/edit | NULL | 2 | |||
29 | 1 | itemAction | Construct/Maintain/Use | Proposal: [RT] Identifies the class/action of the item, e.g. construction, maintainance. For description, please see https://docs.google.com/document/d/1Jr-1DHzdHP0rH77F_Kl8q5HfvJvWiKrFRQwZgZvD3LE/edit | NULL | 2 | |||
30 | 1 | itemAdminContext | Proposal | Proposal: [RT] Identifies the TYPE of item, e.g. proposal, application, intent to award, etc. Could also pull in procurement info. Procurement Category Description, Procurement Category Description code For description, please see https://docs.google.com/document/d/1Jr-1DHzdHP0rH77F_Kl8q5HfvJvWiKrFRQwZgZvD3LE/edit | NULL | 2 | |||
31 | 1 | itemDocumentContext | Vote | Proposal: [RT] Describes how the item is being handled according to the document. Is it a vote? A public hearing? An issue to be reviewed? For description, please see https://docs.google.com/document/d/1Jr-1DHzdHP0rH77F_Kl8q5HfvJvWiKrFRQwZgZvD3LE/edit | |||||
32 | Referenced Organization [M] | refOrganization | 6, 78, 897 | Proposal: [RT] Identifies the mentioned organizations/agencies in the notice and/or item text. | NULL | ||||
33 | identifier | 841 | NULL | ||||||
34 | name | Department of Transportation | AdditionalDescription | ||||||
35 | classification | Agency | NULL | ||||||
36 | identifier | 141 | NULL | ||||||
37 | parentOrganization | 841 | NULL | ||||||
38 | name | Traffic and Planning | NULL | ||||||
39 | classification | Agency Division | NULL | ||||||
40 | 1 | Referenced Addresses [M] | refAddress | 789, 8909, 89 | Proposal: [RT] All addresses stored in the same table. Referenced through a relational table (Below shown in full] | NULL | |||
41 | 1 | complete | Spector Hall, 22 Reade Street, New York, NY | AdditionalDescription | Should use the NYC Geocoder [is there an entry reference ID that can be used instead of including all the forms?] | ||||
42 | 1 | name | Spector Hall | NULL | |||||
43 | 1 | address1 | 22 Reade Street | NULL | |||||
44 | 1 | address2 | NULL | ||||||
45 | 1 | city | New York | NULL | |||||
46 | 1 | state | NY | NULL | |||||
47 | 1 | zip | 10001 | NULL | |||||
48 | 1 | lat | 40.714264 | NULL | |||||
49 | 1 | long | -74.004393 | NULL | |||||
50 | 1 | latLong | 40.714264, -74.004393 | NULL | |||||
51 | 1 | Meeting Details [M] | meetingId | N 150021 PXM | Proposal: [RT] Store each meeting with a separate id in a separate table. The table would include the below field. Address would be stored in a separate table | NULL | 2 | Add to Meeting Object? | |
52 | 1 | startTime | Date / TIME | Source is different for PAST and future notices. | AdditionalDescription. NB. For future notices, this field is being implemented by DCAS. | 1 | |||
53 | 1 | endTime | Date / TIME | Source is different for PAST and future notices. | AdditionalDescription. NB. For future notices, this field is being implemented by DCAS. | 1 | |||
54 | 1 | meetingLocation | 789 | Note: [RT] Like all adresses, stored in separate table, and referenced through a relational table. Details shown below. | NULL | ||||
55 | 1 | complete | Spector Hall, 22 Reade Street, New York, NY | AdditionalDescription. NB. For future notices, this field is being implemented by DCAS. | 1 | ||||
56 | 1 | name | Spector Hall | *can we condense this with one of the addresses for procurement? seems a waste to have empty address fields here and have to add more later | AdditionalDescription | 1 | |||
57 | 1 | address1 | 22 Reade Street | AdditionalDescription | 1 | ||||
58 | 1 | address2 | AdditionalDescription | 1 | |||||
59 | 1 | city | New York | AdditionalDescription | 1 | ||||
60 | 1 | state | NY | AdditionalDescription | 1 | ||||
61 | 1 | zip | 10001 | AdditionalDescription | 1 | ||||
62 | 1 | lat | 40.714264 | NULL | 2 | ||||
63 | 1 | long | -74.004393 | NULL | 2 | ||||
64 | 1 | latLong | 40.714264, -74.004393 | NULL | 2 | ||||
68 | 1 | referenceURL | (text) | AdditionalDescription | 1 | ||||
69 | 1 | videoURL | (text) | AdditionalDescription | 1 | ||||
70 | |||||||||
71 | Sub-Schemas | ||||||||
72 | |||||||||
73 | Public Hearing | ||||||||
74 | 1 | [??] | meetingId | N 150021 PXM | Does the public hearing contain more fields than the meeting object? Does some of the meeting object field fit into the Public hearing object? Does this deserve to be it's own "sub-scema"?) | NULL | 2 | Add to Meeting Object? | |
75 | |||||||||
76 | Property Disposition | ||||||||
77 | 2 | Property Type Code | Proposal: [RT] unique ID per type of property disposition. This should be borrowed from CategoryDescription and CategoryCode from the Procurement Database. | NULL | 2 | ||||
78 | 2 | Property Description | Proposal: [RT] description per type of property disposition. This should be borrowed from CategoryDescription and CategoryCode from the Procurement Database. | NULL | 2 | ||||
79 | 2 | addressInquiry | 245 | Note: [RT] Like all adresses, stored in separate table, and referenced through a relational table. Details shown below. | NULL | - | |||
80 | 2 | complete | Text: "Spector Hall, 22 Reade Street, New York, NY" | Address of Request for procurement | AddressToRequest | - | |||
81 | 2 | name | “Spector Hall” | AddressToRequest | 1 | ||||
82 | 2 | address1 | “22 Reade Street” | AddressToRequest | 1 | ||||
83 | 2 | address2 | AddressToRequest | 1 | |||||
84 | 2 | city | “New York” | AddressToRequest | 1 | ||||
85 | 2 | state | "NY" | AddressToRequest | 1 | ||||
86 | 2 | zip | XXXXX | AddressToRequest | 1 | ||||
87 | 2 | lat | (locationLat:"40.714264") | needs to be computed | NULL | 2 | |||
88 | 2 | long | (locationLon:"-74.004393") | needs to be computed | NULL | 2 | |||
89 | 2 | latLong | (Lat, Lon) | needs to be computed | NULL | 2 | |||
90 | 2 | [??] | Address to Submit URL | http://addresss.local | NULL | - | |||
91 | |||||||||
92 | Court Notices | ||||||||
93 | 2 | [??] | Court Body Name | [Needs Example value] | Note: These appear in the PDFs but do not appear anywhere else. | NULL | - | ||
94 | 2 | [??] | Court Body Code | [Needs Example value] | NULL | - | |||
95 | 2 | [??] | Court County Name | [Needs Example value] | Note: These appear in the PDFs but do not appear anywhere else. | NULL | - | ||
96 | 2 | [??] | Court County Code | [Needs Example value] | NULL | - | |||
97 | 2 | [??] | IA Part | [Needs Example value] | Note: These appear in the PDFs but do not appear anywhere else. | NULL | - | ||
98 | 2 | [??] | Court Index Number | (number) | Note: These appear in the PDFs but do not appear anywhere else. | NULL | - | ||
99 | 2 | [??] | Court - Type of notice | [Needs Example value] | Note: This might be duplicate. Do court types have their own special type of notice. | NULL | - | ||
100 | 2 | Court Notice Body | (text) | NULL | - | ||||
101 | 2 | URL related to notice | (text) | Note: This is a proposed field. | NULL | - | |||
102 | 2 | Map Image | [Needs Example value] | Note: this is a proposed field. This would be an img file or attachment. | NULL | - | |||
103 | 2 | pointOfContactName | Beverly G. Matthews | ContactName from Proc | 0 | ||||
104 | 2 | pointOfContactPhone | 2123413464 | Phone | 0 | ||||
105 | 2 | pointOfContactEmail | beverly.matthews@acs.nyc.gov | 0 |