Custom Scheduled Jobs
This section contains documentation on Custom Scheduled jobs, or jobs that were written specifically for this EpiServer implementation. If a scheduled job is not included on this list but can be found in the scheduled jobs section of EpiServer's administration console, it is not a custom scheduled job and the documentation should be referenced on EpiServer's website. More detail for each scheduled job can be found below.
- Sitemap Scheduled Job
- Import Club Amenities + Event Types
- Geo Location Import
- Load Benefits Finder Data
- Migrate EzPublish Content
- Unused Content Removal
- Import Club Addresses
Sitemap Scheduled Job
As documented on the SEO page, this job will update the scheduled jobs stored on the Sitemap Settings page, which will be returned as XML if the sitemap is requested. It will reference every published page on the site that is not marked "no index/no follow" and include the images referenced on that page as well.
Import Club Amenities + Event Types
Import club amenities and event types used in search results. These can be assigned to clubs on the Club Search Data tab of the club home page and new values can be added (or display values can be updated) on the Search tab of the Global Settings Page. The file should be named "owned_amenities.csv" and located in a folder named "Amenities_Data" under the "For All Sites" folder. There should also be an SVG file in that directory named "default_icon.svg" to use as a default when the new Value Item blocks are created. Running the job will create the blocks and update club home pages. The value item blocks must then be added to the correct location on the global settings page.
CSV file column | Description |
Club | Club name. |
Entity Number | Club entity number. |
Active Inactive | "Active" or "Inactive" |
Value | The Key value of the Value Items. ex: business-services |
Type | "amenity" or "event-type" |
Geo Location Import
Import geolocation data (latitude and longitude values) for both owned and/or alliance clubs using CSV files. The files should be named "alliance_geolocation.csv" and "owned_geolocation.csv" respectively and located in a folder named "Geolocation_Data" under the "For All Sites" folder in the content tree.
alliance_geolocation.csv
CSV file column | Description |
AllianceID | |
Latitude | |
Longitude |
owned_geolocation.csv
CSV file column | Description |
EntityCode | |
ClubName | |
Latitude | |
Longitude |
Load Benefits Finder Data
Import benefits finder-related data for owned and alliance clubs using 4 CSV files.
alliance_club_data.csv
Import alliance club meta data, such as address, phone number, relationship, etc.
CSV file column | Description |
AllianceID | |
Club Name | |
Entity Number | |
Benefit Category | |
Tier | |
Property Type | |
Community | |
Street Address | |
City | |
State | |
Country | |
Zip | |
Phone | |
Extension |
alliance_prospect_benefits.csv
Import alliance benefits for the benefits finder prospecting tool.
CSV file column | Description |
Alliance ID | |
Entity Number | |
Club Name | |
Prospect Golf Group 1 | |
Prospect Golf Benefit 1 | |
Prospect Golf Disclaimer 1 | |
Prospect Golf Group 2 | |
Prospect Golf Benefit 2 | |
Prospect Golf Disclaimer 2 | |
Prospect Dining Group 1 | |
Prospect Dining Benefit 1 | |
Prospect Dining Disclaimer 1 |
owned_club_data.csv
Import owned club meta data, such as tier, community, club type, etc.
CSV file column | Description |
Entity Number | |
Tier | |
Type | |
Community |
owned_prospect_benefits.csv
Import owned club benefits for the benefits finder prospecting tool.
CSV file column | Description |
Entity Number | |
Club Name | |
Prospect Golf Group 1 | |
Prospect Golf Benefit 1 | |
Prospect Golf Disclaimer 1 | |
Prospect Golf Group 2 | |
Prospect Golf Benefit 2 | |
Prospect Golf Disclaimer 2 | |
Prospect Dining Group 1 | |
Prospect Dining Benefit 1 | |
Prospect Dining Disclaimer 1 |
Migrate EzPublish Content
Unused Content Removal
Import Club Addresses
CSV file column | Description |