Ask Your Question
0

InnoVia to Paragon Conversion: 196 StandardNames Fields Missing

asked 2016-08-19 11:42:40 -0500

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

"The promise of RETS is to lower costs and increase the availability of real estate software by providing a single standard across the country and even internationally." The backbone of this standard is StandardNames. See: http://www.realtor.org/retsorg.nsf/pa...

Accordingly as an example "residential" RETS inquiry, I used phRETS standard designated resource=Property, Paragon's phRETS class=RE_1, and setting StandardNames=1 to implement a server-side exchange of data from Paragon to my client's web site. The process works fine. However, the data feed is deficient because the Paragon output only provides 55 StandardNames fields, or about 23%, of the 248 StandardNames fields available from the Innovia 'RETS server.

In the alternative, without using StandardNames fields and relying on RETS Metadata by shutting StandardNames off [StandardNames=0], I will need to know which of the 19,422 Paragon Metadata field mappings, or combinations thereof, translate directly to all of Innovia's 240 StandardNames fields. This is necessary because StandardNames must either be on or off. Mixing and matching is not possible.

A "Best Parcrice" analysis would strongly suggest to continue using the industry-wide StandardNames protocol.

Therefore, I would appreciate Paragon providing the missing 196 Innovia StandardNames fields shown below:

ListAgentAgentID,ListAgentOfficeID,ListingAgentID,ListingFirmID,DisabilityFeatures,EquipmentAndAppliances,LotDescription,OccupantRestrictions,WaterAccessDesc,WaterRestrictions,AcresCommon,AgentStatus,Amenities,AnchorYN,AnnualExpenses,AppxTtlSqBlGd,ApxFinSqFtTotal,AssessmentAmount,AssignedParkingYN,AuctionDate,AuctioneerLicNo,AuctionInfo,AuctionPriceDetermination,AuctionTime,AVMYN,BasementBedrooms,BasementYN,Bath34Level,Bath34Size,Baths,Baths141stFloor,Baths143rdFloor,Baths144thFloor,Baths341stFloor,Baths342ndFloor,Baths343rdFloor,Baths344thFloor,Baths34Basement,BathsPartial,Bedroom1Level,Bedroom2Level,Bedroom2Size,Bedroom3Level,Bedroom3Size,Bedroom4Level,Bedroom4Size,Bedroom5Level,Bedroom5Size,BedRoomMasterDimensions,Block,BlogYN,BuildingCert,BuildingNumber,CableCo,CoListAgent,CondoName,CondoOwnersAssociationDues,Construction,ConstructionStatus,CoOpYN,County,DatePhoto,DatePriceChange,DeedPage,DeedRestrictions,DenLevel,DenSize,DevelopmentDesc,DiningRoomLevel,DiningRoomSize,DisplayFlagAddress,DisplayFlagListing,DocsAvailable,Driveway,Electric,FamilyRoomLevel,FamilyRoomSize,FeeIncludes,Financing,FinishedAboveGrade,FloodZone,Floor1Bedrooms,Floor2Bedrooms,Floor3Bedrooms,Floor4Bedrooms,FloorNumber,Floors,Footprint,Foundation,FuelCo,FullBath1stFloor,FullBath2ndFloor,FullBath3rdFloor,FullBath4thFloor,FullBathBasement,FullBathLevel,FullBathSize,GarageCapacityNumber,GarageType,HalfBath2Level,HalfBaths1stFloor,HalfBaths2ndFloor,HalfBaths3rdFloor,HalfBaths4thFloor,HalfBathsBasement,HalfBathSize,HeatFuel,HERIndex,HouseColor,InsuranceExpenses,KitchenLevel,KitchenSize,LandDesc,LandGains,LandOwned,LimitedCommonArea,ListingOffice,LivingRoomLevel,LivingRoomSize,Lot,LotSqFt,ManagementExpenses,MapCoordinates,MLSType,MobileHomeMake,ModelName,MonthlyAssocFees,MonthlyFee,MustMoveYN,Negotiable,OfficeIDX,OfficeLevel,OfficeSize,OfficeStatus,OfficialTown,Other,OtherRoom1Size,OtherRoom2Level,OtherRoom2Size,OtherRoom3Level,OtherRoom3Size,OtherRoomLevel,ParcelAccessRowYN,ParkApprovalYN,ParkName,PhoneCo,PhotoCount,PhotoModificationTimestamp,PrevisiteVirtualTourURL,PrevisiteVirtualTourYN,PricePerAcre,PricePerSF,PropertyFormat,PropertyID,PropertyType,PUDYN,RentalAmount,RentedYN,ResortYN,RespAuctioneer,RoadFrontage,RoadFtgYN,Roads,RowForOtherParcel,ROWLength,ROWWidth,SeasonalYN,SerialNumber1,Sewer,SqFtFinishedBelowGrade,StatusActualNumber,StreetType,Submarket,SuitableUse,SurveyedYN,TaxAmount,TaxBook,TaxExpenses,TaxIDNumberSpanVT,TaxRate,TaxTBD,TaxYear,TimeshareFractionalOwn,TimesharePercent,TotalBaths,TransferFee,UnitsPerBuilding,UtilityRoomLevel,UtilityRoomSize,VillageName,VirtualTourURL,VirtualTourYN,WaterBodyName,WaterCF,WaterFrontage,WaterHeater,WaterType,Weeks,YearAssessed

edit retag flag offensive close merge delete

Comments

in the word document P-Paragon RETS DEveloper Start Guide on page 10 it states NOTE: Standard Name values are limited and many of the fields will not have this value populated. Many clients choose to use the System Name values to reference the fields. so this is not a true RETS compliant feed.

bscdata gravatar imagebscdata ( 2016-08-22 13:28:55 -0500 )edit

The issue is that my NEREN feed never provided my company access to Innovia Metadata. Therefore, with this project conversion, a translation to all of Innovia's StandardNames to Paragon Metadata should have been identified by Qualtity Assurance to the Project Manager as a requirement. Still waiting.

dcgllc gravatar imagedcgllc ( 2016-08-22 19:40:15 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2016-08-31 11:19:35 -0500

The fields identified are the SystemName values provided by the outgoing MLS vendor, not RETS StandardNames. Additional information has been provided directly by the local MLS.

edit flag offensive delete link more

Comments

A similar question, http://vendorsupport.paragonrels.com/..., has more information. The MLS has additional information to share.

vendorsupport gravatar imagevendorsupport ( 2016-09-16 11:07:52 -0500 )edit

There was NO conversion project manager. As a result, there is NO document showing NEREN Standard Names mapping to Paragon cryptic field names. Paragon's Standard Names have NO match to 196 NEREN Innovia Standard Names. Thus, hundreds of real estate vendors wasted time creating their own mapping.

dcgllc gravatar imagedcgllc ( 2017-07-12 09:23:57 -0500 )edit
Login/Signup to Answer

Question Tools

2 followers

Stats

Asked: 2016-08-19 11:42:40 -0500

Seen: 990 times

Last updated: Aug 31 '16