The Travel Profile resource represents a Concur Travel profile that contains travel-related information about a user.
Detailed descriptions of requests and responses are available in the documentation for each HTTP method.
This endpoint provides travel profile information for the specified user. The travel profile includes information such as the user’s identity, contact information, rate preferences and discount codes, preferences by travel type, and custom fields.
https://{InstanceURL}/api/travelprofile/v2.0/profile
All request parameters are optional. To identify a specific user by Login ID or XML Sync ID, you can specify the following request parameters:
| Parameter Name | Parameter Type | Data Type | Description |
|---|---|---|---|
userid_type |
Path |
string |
The type of user identification to use. Possible values are: login and xmlsyncid |
userid_value |
Path |
string |
The user’s Login ID or XML Sync ID, depending on which user type is selected. This parameter must be provided in conjunction with the userid_type parameter. |
application/xml
Authorization: OAuth {access_token}
Where access_token is the OAuth 2.0 access token of the user whose travel profile information you want to retrieve.
Creating/Updating a Profile uses the same model as what is retrieved.
FirstName
LastName
TravelConfigID
(used to verify agency and Company access to create user)LoginID
Password
RuleClass
(uses default rule class if not provided)application/xml
Authorization: OAuth {access_token}
Where access_token
is the OAuth 2.0 access token of the user whose travel profile information you want to retrieve or update.
The complete schema definition is available here: Travel Profile XSD.
SAP Concur reserves the right to change the XSD. Reading/writing strictly to the XSD will result in breakage as new XML elements are added.
The Profile root element contains:
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
NamePrefix |
string |
The user’s name prefix. Format: nvarchar(60) | - | - | - |
FirstName |
string |
The user’s first name. Format: nvarchar(60) | - | Required | - |
MiddleName |
string |
The user’s middle name. Format: nvarchar(60) | - | - | - |
LastName |
string |
The user’s last name. Format: nvarchar(60) | - | Required | - |
NameSuffix |
string |
The user’s name suffix. Format: nvarchar(60) | - | - | - |
PreferredName |
string |
The user’s preferred name. Format: nvarchar(60) | - | - | - |
JobTitle |
string |
The user’s job title. Format: nvarchar(255) | - | - | - |
CostCenter |
string |
The user’s cost center. Format: nvarchar(25) | - | - | Requires Company Details scope. |
CompanyEmployeeID |
string |
The user’s employee ID. Format: nvarchar(48) | - | - | Requires Company Details scope. Must be unique in the company. |
Division |
string |
The user’s division. Format: nvarchar(60) | - | - | Requires Company Details scope. Must already be setup in the company configuration. |
PreferredLanguage |
string |
The user’s preferred language locale. Example: United States English is en-US. Format: varchar(20) | - | - | - |
EReceiptOptIn |
boolean |
Whether the user has opted in to receive e-receipts. Format: true\false | - | - | |
HasOpenBooking |
boolean |
Whether the user has the TripLink User (formerly Open Booking User) permission. Format: true\false | Cannot Update | - | - |
CountryCode |
string |
The country code in from the ISO 3166-1 alpha-2 country code specification. Format: char(2) | Cannot Update | - | - |
CompanyName |
string |
The user’s company name. Format: nvarchar(255) | Cannot Update | - | - |
CompanyID |
string |
The user’s company ID. Format: varchar(255) | Cannot Update | - | Requires Company Details scope. |
RuleClass |
string |
The user’s rule class. Format: nvarchar(60) | - | - | Must already be setup in the company. |
TravelConfigID |
string |
The user’s TravelConfig. Format: varchar(255) | - | Required | - |
MedicalAlerts |
string |
The user’s medical alerts. Format: nvarchar(255) | - | - | Requires Medical Alerts Scope. |
AgencyNumber |
string |
The TravelConfig’s Agency IATA Number. Format: varchar(255) | Cannot Update | - | - |
SearchID |
string |
The user’s Search ID. Format: varchar(64) | - | - | - |
GDSProfileName |
string |
The user’s GDS profile name. Format: varchar(60) | - | - | Requires TMC Specific scope. |
SabreProfileId |
string |
The user’s Sabre Travel Profile Id. Format: varchar(60) | - | - | Requires TMC Specific scope. |
UUID |
string |
The user’s Unique Identifier. Format: GUID, 32 characters | Cannot Update | - | Requires TMC Specific scope. |
NOTE: If MiddleName is provided, the NoMiddleName flag in TSAInfo section is set to false.
The emergency contact information provided.
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
Name |
string |
The emergency contact name Format: nvarchar(255) | - | - | - |
Relationship |
string |
The relationship to the user. Values are: Spouse, Brother, Parent, Sister, LifePartner, Other | - | - | - |
Phone |
list |
- | - | - | If multiple values of the same telephone type are provided, only the last one will be saved. See below for the list elements. |
Address |
Address |
Street Address. Format: nvarchar(max) | - | - | - |
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
Street |
string |
Street Address. Format: nvarchar(max) | - | - | - |
City |
string |
The city name. Format: nvarchar(30) | - | - | - |
StateProvince |
string |
The state or province. Format: nvarchar(30) | - | - | - |
CountryCode |
string |
The country code in from the ISO 3166-1 alpha-2 country code specification. Format: char(2) | - | - | - |
PostalCode |
string |
The postal code. Format: nvarchar(20) | - | - | - |
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
PhoneNumber |
string |
The emergency contact’s phone number. Format: nvarchar(60) | - | - | No unicode characters. |
Type |
string |
This contains a “type” attribute with values of DayTime or Alternate. | Required | Required | - |
The Telephones parent element contains a Telephone child element for each included telephone. The Telephone element has the attributes shown in the Response Class section and contains the following child elements:
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
Type attribute |
string |
Type of phone. Values are: Home, Work, Fax, Pager, Other, and Cell | required | required | - |
ContactOptIn attribute |
boolean |
Whether the user has opted in to being contacted on this phone. Only appears when the phone type is Cell. Format: true\false | - | - | - |
PrimaryMobile attribute |
boolean |
This is the user’s preferred mobile device. Format: true\false | - | - | - |
CountryCode |
string |
The country code in from the ISO 3166-1 alpha-2 country code specification. Format: Char(2) | required (Cell) | required (Cell) | Required for Cell types. |
PhoneNumber |
string |
The phone number as entered by the user, which may contain characters such as () or -. Format: nvarchar(60) |
required (Cell) | required (Cell) | Required for Cell types. |
Extension |
string |
The phone extension. Format: nvarchar(60) | - | - | - |
MobileDevice |
string |
The OS of the mobile device. Values are: Android Phone Android Tablet Blackberry iOS Phone iOS Tablet Not a smartphone Other iOS device Other smartphone Unknown Window Mobile |
- | - | - |
MobileName |
string |
The name the user assigned to the mobile device. Format: nvarchar(255) | - | - | - |
NOTES
CountryCode
, DeviceName
, DeviceType
, ContactOptIn
, IsPrimaryMobile
PrimaryMobile
:
PrimaryMobile
specified in changing cell phones, then all cell phone changes will be rejected. If only one (1) cell phone is provided, it is marked as primary.The Addresses
parent element contains an address child element for each included address. The address element has the attributes shown in the response class section and contains the following child elements:
NOTE: The values returned for the Address child elements are as entered by the user. The fields do not enforce formatting and may have a wide variety of values.
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
Type attribute |
string |
Address type. Values are: Home or Work | required | required | If multiple values are provided for either address type, the last one will be the one saved in the creation/update. |
Street |
string |
Street Address. Format: nvarchar(max) | - | - | - |
City |
string |
The city name. Format: nvarchar(30) | - | - | - |
StateProvince |
string |
The state or province. Format: nvarchar(30) | - | - | - |
CountryCode |
string |
The country code in from the ISO 3166-1 alpha-2 country code specification. Format: char(2) | - | - | - |
PostalCode |
string |
The postal code. Format: nvarchar(20) | - | - | - |
Longitude |
string |
Longitude value of Work Address. | Cannot Update | - | - |
Latitude |
string |
Latitude value of Work Address. | Cannot Update | - | - |
The NationalIDs
parent element contains a NationalID
child element for each included National ID. The NationalID
element contains the following child elements:
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
NationalIDNumber |
string |
The user’s national identification number. Format: nvarchar(100) | - | - | No unicode accepted. Only saves one national ID value. If multiple are provided, W016 warning message is returned. |
IssuingCountry |
string |
The country the national ID was issued in. Format: varchar(2) | - | - | - |
Expiration |
date |
The expiration date of the national ID. Format: YYYY-MM-DD |
- | - | Min - 01/01/1753, Max - 12/31/9999 |
NOTE: Only one National ID can be accepted.
The DriversLicenses
parent element contains a DriversLicense
child element for each included licenses.
DriversLicense
element contains the following child elements:| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
DriversLicenseNumber |
string |
The user’s driver license identification number. Format: nvarchar(100) | - | - | Only saves one Drivers License Number value. If multiple are provided, W016 warning message is returned. |
IssuingCountry |
string |
The country the license was issued in. Format: varchar(2) | - | - | - |
IssuingState |
string |
The state the license was issued in. Format: nvarchar(30) | - | - | - |
Expiration |
date |
The expiration date of the license. Format: YYYY-MM-DD |
- | - | Min - 01/01/1753, Max - 12/31/9999 |
NOTE: Only one Drivers License can be accepted.
A flag which is triggered automatically when adding a new passport to a user.
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
HasNoPassport |
boolean |
Format: true\false. | - | If passport value added, then this value becomes false. |
A list of passports in the user’s profile:
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
PassportNumber |
string |
The user’s passport number. Format: nvarchar(100) | Required | Required | - |
PassportNationality |
string |
The user’s passport nationality. Format: char(2) | Required | Required | - |
PassportExpiration |
date |
The date the user’s passport expires. Format: YYYY-MM-DD |
- | - | Min - 01/01/1900, Max - 06/06/2079 |
PassportDateIssued |
date |
The date the user’s passport was issued. Format: YYYY-MM-DD |
- | - | Min - 01/01/1900, Max - 06/06/2079 |
PassportCityIssued |
string |
The city the user’s passport was issued in. Format: nvarchar(60) | - | - | - |
PassportCountryIssued |
string |
The country code in from the ISO 3166-1 alpha-2 country code specification. Format: char(2) | - | - | - |
NOTE: there can only be 2 passports associated to a user. If more than two passports are provided, W016 warning message is returned.
A list of visas in the user’s profile.
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
VisaNationality |
string |
The user’s visa nationality. Format: char(2) | Required | Required | - |
VisaNumber |
string |
The user’s visa nationality. Format: nvarchar(100) | Required | Required | - |
VisaType |
string |
The user’s visa type. Values are Unknown, SingleEntry, DoubleEntry, MultiEntry, ESTA, ETA, and SchengenVisa. | - | - | - |
VisaDateIssued |
date |
The date the user’s visa was issued. Format: YYYY-MM-DD |
- | - | Min - 01/01/1900 Max - 06/06/2079 |
VisaExpiration |
date |
The date the user’s visa expires. Format: YYYY-MM-DD |
- | - | Min -01/01/1900 Max - 06/06/2079 |
VisaCityIssued |
string |
The city the user’s visa was issued in. Format: nvarchar(60) | - | - | - |
VisaCountryIssued |
string |
The country code in from the ISO 3166-1 alpha-2 country code specification. Format: char(2) | - | - | - |
NOTE: Visas will sync with existing visas. Any existing Visas not provided in the list will be deleted.
The EmailAddresses
parent element contains an EmailAddress
child element for each included email address. It contains the following child element:
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
EmailAddress |
string |
The user’s email address. Format: Varchar(255) | - | - | - |
Contact attribute |
boolean |
The Contact attribute specifies whether the email address should be used for travel notifications. Format: true\false. | - | - | - |
Type attribute |
string |
The type of email address. Values are: Business, Personal, Supervisor, TravelArranger, Business2, Other1, and Other2. | Required | Required | Supervisor and TravelArranger cannot be updated. Only 1 of each type is allowed. W016 Error is returned |
The RatePreferences parent element contains the following child element:
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
AAARate |
boolean |
Whether the user is eligible for the AAA rate. Format: true\false | - | - | - |
AARPRate |
boolean |
Whether the user is eligible for the AARP rate. Format: true\false | - | - | - |
GovtRate |
boolean |
Whether the user is eligible for the Government rate. Format: true\false | - | - | - |
MilitaryRate |
boolean |
Whether the user is eligible for the Military rate. Format: true\false | - | - | - |
The DiscountCodes
parent element contains a DiscountCode
child element for each included discount code.
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
DiscountCode |
string |
The discount code for the specified vendor. | - | - | unable to update |
Vendor attribute |
string |
Specifies the name of the vendor for the discount code. | - | - | unable to update |
NOTE: Discount code elements are not available to create or update.
The Air
parent element contains the user’s air travel preferences and contains the following child elements:
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
AirMemberships |
- | The AirMemberships element only appears if the request came from a travel supplier for this travel type, or from a TMC. This element contains AirMembership child elements. | - | - | - |
Seat |
- | This element contains air seat child elements. | - | - | - |
Meals |
string |
This parent element contains the MealCode child element that indicates the meal preference of the traveler. See Reference for possible values. | - | - | Defaults to Regular Meal |
HomeAirport |
string |
The user’s home airport. varchar(3) | - | - | Must be an existing IATA code. |
AirOther |
string |
Other Air related description | - | - | - |
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
VendorCode |
string |
The code for the vendor that manages the loyalty program. varchar(2) | Required | Required | Must be a valid VendorCode for the membership type. This list can be made available upon request. |
AccountNo |
string |
The user’s account identifier in the loyalty program. varchar(60) | Required | Required | - |
Status |
string |
Name of the user’s current level in the loyalty program. varchar (100) | - | - | - |
StatusBenefits |
string |
Description of a benefit of the loyalty program at the current status. | - | - | - |
PointTotal |
string |
The user’s total number of points in the loyalty program. | - | - | - |
SegmentTotal |
string |
The user’s total segments in the loyalty program. | - | - | - |
NextStatus |
string |
Name or description of next higher status level in the loyalty program. | - | - | - |
PointsUntilNextStatus |
string |
Loyalty points required to next status level. | - | - | - |
SegmentsUntilNextStatus |
string |
Booking segments to next status level. | - | - | - |
IsSenator |
boolean |
Lufthansa specific field. Format: true\false | - | - | - |
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
InterRowPositionCode |
string |
Preferred position in an airplane row. Format: Window , Aisle , Middle , DontCare . |
- | - | - |
SectionPositionCode |
string |
Preference for position in plane. Format: Bulkhead , Forward , Rear , ExitRow , DontCare . |
- | - | - |
The Rail
parent element contains the user’s rail travel preferences and contains the following child elements:
| Name | Data Type | Description | Update | Create | Comments | |
|---|---|---|---|---|---|---|
Seat |
string |
This element contains seat preferences. Format: Aisle , Window , DontCare |
- | - | - | |
Coach |
string |
This element contains coach preferences. Format: Compartment , Coach , CoachWithTable , DontCare |
- | - | - | |
NoiseComfort |
string |
This element contains noise comfort preferences. Format: QuietSpace , MobileSpace , DontCare |
- | - | - | |
Bed |
string |
This element contains bed preferences. Format: Lower , Upper , Middle , DontCare |
- | - | - | |
BedCategory |
string |
This element contains bed category preferences. Format: WomenOnly , MenOnly , DontCare |
- | - | - | |
Berth |
string |
This element contains berth preferences. Format: Lower , Upper , Middle , DontCare |
- | - | - | |
Deck |
string |
This element contains deck preferences. Format: Lower , Upper , DontCare |
- | - | - | |
SpaceType |
string |
This element contains space type preferences. Format: Panorama , SeatWithTable , Solo , Salon , Kiosk , InclineSeat , DuoSideBySide , DuoFaceToFace , Club6 , Club4 , Carre , DisabledCompanionSpace , DontCare |
- | - | - | |
FareSpaceComfort |
string |
This element contains fare space comfort preferences. Format: DedicatedBusiness , Business , IntermediateLeisure , Leisure , StandardLeisure , DontCare |
- | - | - | |
SpecialMeals |
string |
This element contains special meal preferences. Format: LowFat , LowSalt , GlutenFree , Diabetic , Muslim , Kosher , Vegetarian , VegetarianLactoOvo , DontCare |
- | - | - | |
Contingencies |
string |
This element contains contingencies preferences. Format: Bike , WomenOnly , WheelchairSpace , DontCare |
- | - | - | |
RailMemberships |
- | This element contains RailMembership child elements | - | - | - | - |
| Name | Data Type | Description | Update | Create | Comments | |
|---|---|---|---|---|---|---|
VendorCode |
string |
The code for the vendor that manages the loyalty program. varchar(2) | Required | Required | Must be a Valid Vendor Code for the Membership Type. This list can be made available upon request. | |
AccountNo |
string |
The user’s account identifier in the loyalty program. varchar(60) | Required | Required | See Below. | |
Status |
string |
Name of the user’s current level in the loyalty program. varchar (100) | - | - | - | |
StatusBenefits |
string |
Description of a benefit of the loyalty program at the current status. | - | - | - | |
PointTotal |
string |
The user’s total number of points in the loyalty program. | - | - | - | |
SegmentTotal |
string |
The user’s total segments in the loyalty program. | - | - | - | |
Expiration |
DateTime |
The user’s expiration date in the loyalty program. Min - 01/01/1753, Max - 12/31/9999 | - | - | - | - |
NextStatus |
string |
Name or description of next higher status level in the loyalty program. | - | - | - | |
PointsUntilNextStatus |
string |
Loyalty points required to next status level. | - | - | - | |
SegmentsUntilNextStatus |
string |
Booking segments to next status level. | - | - | - | |
BahnCardClass |
string |
Bahn card class. Valid values are First and Second. | - | - | - | |
BahnCardType |
string |
Bahn card type. Valid values include NA (for non-rail programs), Card25, Card50, Card100, Business25, and Business50. | - | - | - |
The Car
parent element contains the user’s car travel preferences. It contains the following child elements:
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
CarSmokingCode |
string |
Smoking car preferred. Format: DontCare , NonSmoking , Smoking |
- | - | - |
CarGPS |
boolean |
Car GPS preference. Format: true\false. | - | - | - |
CarType |
string |
Car type preference. Values are: DontCare Mini Economy EconomyHybrid Compact CompactHybrid Intermediate IntermediateHybrid Standard StandardHybrid FullSize FullSizeHybrid MiniVan Luxury Premium StandardSUV IntermediateSUV FullSizeSUV FullSizePickup Specialized |
- | - | - |
CarMemberships |
- | The CarMemberships element only appears if the request came from a travel supplier for this travel type, or from a TMC. This element contains CarMembership child elements for each included membership. | - | - | - |
CarOther |
string |
Other Car related description. Format: varchar(30) | - | - | - |
CarSkiRack |
boolean |
Car ski rack preference. Format: true\false. | - | - | |
CarTransmission |
string |
Car transmission type. Values are: DontCare , Automatic , Manual |
- | - | - |
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
VendorCode |
string |
The code for the vendor that manages the loyalty program. varchar(2) | Required | Required | Must be a Valid Vendor Code for the Membership Type. This list can be made available upon request. |
AccountNo |
string |
The user’s account identifier in the loyalty program. varchar(60) | Required | Required | See Below. |
Status |
string |
Name of the user’s current level in the loyalty program. varchar (100) | - | - | - |
StatusBenefits |
string |
Description of a benefit of the loyalty program at the current status. | - | - | - |
PointTotal |
string |
The user’s total number of points in the loyalty program. | - | - | - |
SegmentTotal |
string |
The user’s total segments in the loyalty program. | - | - | - |
Expiration |
DateTime |
The user’s expiration date in the loyalty program. | - | - | Min - 01/01/1753, Max - 12/31/9999 |
NextStatus |
string |
Name or description of next higher status level in the loyalty program. | - | - | - |
PointsUntilNextStatus |
string |
Loyalty points required to next status level. | - | - | - |
SegmentsUntilNextStatus |
string |
Booking segments to next status level. | - | - | - |
The Hotel
parent element contains the user’s hotel travel preferences. It contains the following child elements:
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
SmokingCode |
string |
Smoking room preference. Values: DontCare , NonSmoking ,Smoking |
- | - | - |
HotelMemberships |
- | This parent element only appears if the request came from a travel supplier for this travel type, or from a TMC. This element contains HotelMembership child elements for each included membership. | - | - | - |
RoomType |
string |
Hotel room preference. Values are: DontCare , King , Queen , Double , Twin , Single , Disability |
- | - | - |
HotelOther |
string |
Other Hotel related description. Format: varchar(30) | - | - | - |
PreferFoamPillows |
boolean |
Whether the user prefers foam pillows. Format: true\false. | - | - | - |
PreferCrib |
boolean |
Whether the user prefers to have a crib. Format:true\false. | - | - | - |
PreferRollawayBed |
boolean |
Whether the user prefers to have a rollaway bed. Format:true\false. | - | - | - |
PreferGym |
boolean |
Whether the user prefers a hotel with a gym. Format:true\false. | - | - | - |
PreferPool |
boolean |
Whether the user prefers a hotel with a pool. Format:true\false. | - | - | - |
PreferRestaraunt |
boolean |
Whether the user prefers a hotel with a restaurant. Format:true\false. | - | - | - |
PreferWheelchairAccess |
boolean |
Whether the user requires wheelchair access. Format: true\false. | - | - | - |
PreferAccessForBlind |
boolean |
Whether the user requires a room with access for blind guests. Format:true\false. | - | - | - |
PreferRoomService |
boolean |
Whether the user prefers a hotel with room service. Format:true\false. | - | - | - |
PreferEarlyCheckIn |
boolean |
Whether the user prefers a hotel with early check in. Format:true\false. | - | - | - |
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
VendorCode |
string |
The code for the vendor that manages the loyalty program. varchar(2) | Required | Required | Must be a Valid Vendor Code for the Membership Type. This list can be made available upon request. |
AccountNo |
string |
The user’s account identifier in the loyalty program. varchar(60) | Required | Required | See Below. |
Status |
string |
Name of the user’s current level in the loyalty program. varchar (100) | - | - | - |
StatusBenefits |
string |
Description of a benefit of the loyalty program at the current status. | - | - | - |
PointTotal |
string |
The user’s total number of points in the loyalty program. | - | - | - |
SegmentTotal |
string |
The user’s total segments in the loyalty program. | - | - | - |
Expiration |
DateTime |
The user’s expiration date in the loyalty program. | - | - | Min - 01/01/1753, Max - 12/31/9999 |
The CustomFields
parent element contains a CustomField
child element for each field.
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
CustomField |
string |
The value of the custom field. Format: varchar(255) | - | - | - |
Name attribute |
string |
The name of the custom field. Format: varchar(255) | Required | Required | - |
A list of users associated to a user:
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
FirstName |
string |
The Arranger/Manager’s first name. Format: varchar(60) | Cannot Update | - | - |
LastName |
string |
The Arranger/Manager’s last name. Format: varchar(60) | Cannot Update | - | - |
EmailAddress |
string |
The Arranger/Manager’s email address. Format: varchar(255) | Cannot Update | - | - |
LoginId |
string |
The Login Id for Arranger/Manager | Required | Required | - |
Type attribute |
string |
The Arranger/Manager’s role. Values are: Arranger, Manager | Required | Required | - |
PrimaryIndicatorFlag attribute |
boolean |
For Arrangers type, denotes the primary arranger. Format: true\false. | - | - | - |
NOTES:
FirstName
, LastName
, and Email
cannot be updated.Managers
and Arrangers
must be in the same company of the user to be assigned.PrimaryIndicatorFlag
is sent in as true, the arranger will be marked as primary.A list of sponsors associated to a user:
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
NonEmployeeUserType |
string |
The non-employee’s user type. Values are: Contractor , Student/Intern , Candidate for Hire , Invitational Traveler , Dependent/Spouse , Board Member , Other |
Required | Required | - |
SponsorName |
string |
The sponsor’s name. Format: varchar(255) | Cannot Update | - | - |
SponsorshipStartDate |
date |
The sponsorship start date. Format: YYYY-MM-DD |
Required | Required | - |
SponsorshipEndDate |
date |
The sponsorship end date. Format: YYYY-MM-DD |
Required | Required | - |
LoginID |
string |
The sponsor’s name. Format: varchar(255) | Required | Required | - |
NOTES:
SponsorshipEndDate
must be after SponsorshipStartDate
The Transportation Security Administration (TSA) details provided.
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
Gender |
string |
The user’s gender. Values are: Male , Female |
- | - | - |
DateOfBirth |
date |
The user’s date of birth. Format: YYYY-MM-DD . Min - 01/01/1900, Max - 06/06/2079 |
- | - | - |
NoMiddleName |
boolean |
Format: true/false |
- | - | - |
PreCheckNumber |
string |
The user’s pre-check number. Format: varchar(255) | - | - | - |
RedressNumber |
string |
The user’s redress number. Format: varchar(255) | - | - | - |
NOTE: NoMiddleName
: If the profile has a middle name, NoMiddleName
overrides to false
A list of unused tickets associated to a user
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
Carrier |
string |
The vendor’s name. Format: Varchar(255) | Required | Required | - |
TicketNumber |
string |
The unused ticket number. Format: Varchar(255) | Required | Required | - |
RecordLocator |
string |
The unused ticket record locator. Format: Varchar(6) | - | - | - |
BaseFare |
string |
The base fare of the unused ticket. Format: Varchar(255) | - | - | - |
Taxes |
string |
The taxes for the unused ticket. Format: Varchar(255) | - | - | - |
Fees |
string |
The fees for the unused ticket. Format: Varchar(255) | - | - | - |
Currency |
string |
The currency of the unused ticket. Format: Varchar(3) | - | - | - |
TicketType |
string |
The type of unused ticket. Format: Varchar(1) | - | - | - |
IssueDate |
date |
The date of issue for the unused ticket. Format: YYYY-MM-DD . |
- | - | Min - 01/01/1753, Max - 12/31/9999 |
ExpirationDate |
date |
The date of expiration for the unused ticket. Format: YYYY-MM-DD . |
- | - | Min - 01/01/1753, Max - 12/31/9999 |
Notes |
string |
Notes associated to the unused ticket. Format: Varchar(255) | - | - | - |
A list of unused Southwest tickets associated to a user.
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
RecordLocator |
string |
The unused ticket record locator. Format: Varchar(255) | Required | - | - |
TicketAmount |
string |
The amount of the unused ticket. Format: Varchar(255) | - | - | - |
Currency |
string |
The currency of the unused ticket. Format: Varchar(3) | - | - | - |
ExpirationDate |
date |
The date of expiration for the unused ticket. Format: YYYY-MM-DD . |
- | - | Min - 01/01/1753, Max - 12/31/9999 |
A list of advantage memberships associated to a user:
| Name | Data Type | Description | Update | Create | Comments |
|---|---|---|---|---|---|
VendorCode |
string |
The code for the vendor that manages the membership program. Format: Varchar(2) | Required | Required | - |
VendorType |
string |
The vendor type. Values are: Air , Rail , Car , Hotel |
Required | Required | - |
ProgramNumber |
string |
The membership program number. Format: Varchar(20) | Required | Required | - |
OriginCode |
string |
The origin code. Format: Varchar(12) | - | - | - |
DestinationCode |
string |
The destination code. Format: Varchar(12) | - | - | - |
ProgramCode |
string |
The program code. Format: Varchar(20) | Required | Required | - |
ExpirationDate |
date |
Expiration date. Format: YYYY-MM-DD . Min - 01/01/1900, Max - 06/06/2079 |
- | - | - |
OptionCode |
string |
The option code. Format: Varchar(20) | - | - | - |
ProgramName |
string |
The program name. Format: Varchar(20) | Cannot Update | - | - |
NOTES:
VendorType
, VendorCode
, ProgramCode
, and CardNumber
are identified and a warning is thrown.OriginStationCode
and DestinationStationCode
fields are deprecated and should no longer be used. Use OriginCode
and DestinationCode
instead.This error message occurs, when the XML is not formatted in such a way that it can be read.
<Error>
<Message>There is an error in XML document (1, 147).</Message>
<Server-Time>2017-06-22T16:51:37</Server-Time>
<Id>3BDBC49E-8793-4515-BA0E-F9C71ADA7330</Id>
</Error>
The best way to find the cause of the error is by taking the body of your message and comparing it against the Travel Profile XSD. You can use free online sites to validate such as https://www.freeformatter.com/xml-validator-xsd.html
The codes and types of messages that can be returned on updates and creates:
| CODE | Message Type | Notes | Example |
|---|---|---|---|
| S001 | Success | Process completed successfully. | Success, no errors or warnings reported. |
| E001 | No Access | No access to user data. | - |
| E002 | Required Field Missing | The field noted is required for updates or creates, no changes were made. | - |
| W001 | Invalid Regex | The given data does not match the expected regex. | - |
| W002 | Invalid Length | The given data is too long or too short. | - |
| W003 | Not Found In Company | The given user was not found in the company. | - |
| W004 | Duplicate Entry | The given data is duplicated and not allowed. | - |
| W005 | Duplicate LoginId | The given LoginID is duplicated. |
- |
| W006 | Out of Range | The given data is out of range. | - |
| W007 | Field is Required | The given field cannot be cleared. | - |
| W009 | Invalid Account Number | Account number check failed due to length, Luhn, etc. | - |
| W010 | Invalid Vendor Code | Vendor code given is invalid. | - |
| W011 | Cannot Change | The given field cannot be altered. | - |
| W012 | Primary Cell Number Error | Data violates one primary cell phone requirement. | - |
| W013 | Invalid Custom Field | The data provided is invalid for the custom field. | - |
| W014 | Invalid Date Range | The data provided is outside of acceptable date range. | - |
| W015 | Invalid GUID | The GUID is invalid. | - |
| W016 | Too Many Items | There are too many items in the given list. | - |
| W017 | No Access to VendorCode | The user lacks access to the given vendor code. | - |
If incorrect API credentials are provided, the service will return the standard response, e.g. 403 Forbidden. In some cases, the API will return additional information when producing a 400, Bad Request, response. It may contain the following codes in the response’s body:
GET {InstanceURI}/api/travelprofile/v2.0/profile HTTP/1.1
Authorization: OAuth {access token}
GET<EMAIL_ADDRESS>HTTP/1.1
Authorization: OAuth {access token}
GET {InstanceURI}/api/travelprofile/v2.0/profile HTTP/1.1
Authorization: OAuth {access token}
GET<EMAIL_ADDRESS>HTTP/1.1
Authorization: OAuth {access token}
POST https://www.concursolutions.com/api/travelprofile/v2.0/profile HTTP/1.1
Authorization: OAuth {access token}
<ProfileResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" Action="Create"<EMAIL_ADDRESS><General>
<FirstName>William</FirstName>
<LastName>Never</LastName>
<RuleClass>Default Rule Class</RuleClass>
<TravelConfigID>555</TravelConfigID>
</General>
<Password>password123</Password>
</ProfileResponse>
POST https://www.concursolutions.com/api/travelprofile/v2.0/profile HTTP/1.1
Authorization: OAuth {access token}
<ProfileResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" Action="Update"<EMAIL_ADDRESS><General>
<FirstName>Bill</FirstName>
</General>
</ProfileResponse>
This endpoint provides a list of travel profile summaries that have been updated since the specified date. The response is separated into pages.
GET {InstanceURI}/api/travelprofile/v2.0/summary?LastModifiedDate=2015-01-01T01:00:00 HTTP/1.1
Authorization: OAuth {access token}
All request parameters are optional. Available request parameters are as follows:
| Parameter Name | Required/Optional | Parameter Type | Data Type | Description |
|---|---|---|---|---|
LastModifiedDate |
Required | path | string |
The date and time, in UTC, that the profiles must be updated after to be included in the response. Format: YYYY-MM-DDThh:mm:ss |
Page |
Optional | path | string |
The number of pages to retrieve. If the page is outside the number of existing pages, the response elements will be empty |
ItemsPerPage |
Optional | path | string |
The number of travel profiles per page. The maximum value is 200. The default value is 200. |
application/xml
Authorization: OAuth {access_token}
Where access_token
is the OAuth 2.0 access token of the user whose travel profile summaries you want to retrieve. If you want to access company-wide travel profile information, the user account associated with the OAuth 2.0 access token must have an SAP Concur account with one of these roles: Web Services Administrator for Professional or Can Administer for Standard.
The data model of the response for the GET operation. The complete schema definition is also available here: Travel Profile Summary V2 XSD
<ConnectResponse>
<Metadata>
<Paging>
<TotalPages />
<TotalItems />
<Page />
<ItemsPerPage />
<PreviousPageURL />
<NextPageURL />
</Paging>
</Metadata>
<Data>
<ProfileSummary>
<Status />
<LoginID />
<XmlProfileSyncID />
<ProfileLastModifiedUTC />
</ProfileSummary>
</Data>
</ConnectResponse>
The ConnectResponse
root element contains the General
, Telephones
, Addresses
, DriversLicenses
, EmailAddresses
, RatePreferences
, DiscountCodes
, Air
, Car
, Hotel
, and CustomFields
child elements. It has the attributes shown in the response class section.
The Metadata
parent element contains the Paging
child element.
The Paging
parent element contains contains the paging information for the response and it contains the following child elements:
| Element Name | Data Type | Description |
|---|---|---|
| TotalPages | string |
The total number of pages to return. |
| TotalItems | string |
The total number of profiles the query returned. |
| Page | string |
The page number for the set of results in the current response. |
| ItemsPerPage | string |
The number of items set to display per page. |
| PreviousPageURL | string |
The URI to the previous page of results. This element will be empty when there are no previous pages. |
| NextPageURL | string |
The URI to the next set of results. This element will be empty when there are no next pages |
The Data parent element contains a ProfileSummary
child element for each included travel profile.
The ProfileSummary
element contains the profile information for the response and it contains the following child elements:
| Element Name | Data Type | Description |
|---|---|---|
| Status | string |
Current status of the user: Active or Inactive. |
| LoginID | string |
The SAP Concur user login ID. |
| XMLProfileSyncID | string |
The user’s XML Profile Sync ID, if available. |
| ProfileLastModifiedUTC | string |
The date, in UTC, when the travel profile was last modified. Format: YYYY-MM-DDThh:mm:ss. |
This example gets the list of travel profile summaries modified after January 1 2015.
GET {InstanceURI}/api/travelprofile/v2.0/summary?LastModifiedDate=2015-01-01T01:00:00 HTTP/1.1
Authorization: OAuth {access token}
HTTP/1.1 200 OK
Content-Type: application/xml
<ConnectResponse>
<Metadata>
<Paging>
<TotalPages>1</TotalPages>
<TotalItems>2</TotalItems>
<Page>1</Page>
<ItemsPerPage>200</ItemsPerPage>
<PreviousPageURL />
<NextPageURL />
</Paging>
</Metadata>
<Data>
<ProfileSummary>
<Status>Active</Status>
<EMAIL_ADDRESS><XmlProfileSyncID>`string`123</XmlProfileSyncID>
<ProfileLastModifiedUTC>2015-01-01T01:00:00</ProfileLastModifiedUTC>
</ProfileSummary>
<ProfileSummary>
<Status>Inactive</Status>
<EMAIL_ADDRESS><XmlProfileSyncID>`string`456</XmlProfileSyncID>
<ProfileLastModifiedUTC>2015-01-01T01:00:00</ProfileLastModifiedUTC>
</ProfileSummary>
</Data>
</ConnectResponse>


Enter the details of your mission to see which maps are possible.
Alien Structure
Forest
Plains
Riparian
Roadway
Settlement
Urban Block
Urban Close Quarters
Urban Large Structure
Waterfront
Aliens: Abductions
Aliens: Terror Site
Council: Asset Recovery
Council: Bomb Disposal
Council: Target Escort
Council: Target Extraction
EXALT: Covert Data Recovery
EXALT: Covert Extraction
UFO: Crashed
UFO: Landed
Abductor
Assault Carrier
Battleship
Destroyer
Fighter
Harvester
Overseer
Raider
Scout
Terror Ship
Transport


After too long, I've finally got my new blog up. It's still not finished, but it's a start, and I can finally start posting again.
I had to change servers, and in the process PyCS got rather broken; everytime there was a write it segfaulted. These days I don't really know what to do with myself when I encounter a segfault. Anyway, though it looks like PyCS will be able to use PostgreSQL soon, I'm afraid it's too late for me.
So it goes. And, of course, every red blooded web programmer has to make their own blogging software. I should not deny these primitive desires that lie in my heart. I must go where so many have gone before...
Along the way I made an atom exporter for PyDS and PyCS -- the articles are exported from PyDS, and the comments from PyCS. I haven't got comments working, so I haven't imported them to the site; I'll fix that soon. I just needed to get something up.
The underlying software is this wiki, tweaked. I'm not sure if a wiki and a blog really fit together, but we'll see. Maybe before too long I hope to be able to finish all the features that I've started, then package the whole thing up, using it as an experiment in how well I can package a Python web application. But that will wait.
Ah, to post again! (Now I wait, will this post really appear?)


DWP
Page 15
April 2012: Time to work on the Hill and tunnel in earnest. The fascia was re-
Here is a look at the opening in the fascia. An access hatch with a door was originally planned, but this idea took hold.It was simpler and provided an interesting location for viewing trains underground. The tracks are about 12” in from the fascia so a little bit of blasted rock was crafted to frame the opening. Using this opening it is possible to reach all of the otherwise hidden track for cleaning.
Above the opening is some of the plaster cloth hardshell. Scott like to work a lot of the irregular shapes that define the mountain into the hardshell in preparation for rock castings. Naturally, we make a mess doing this, but plaster cleans up pretty easy and if you are thinking a head, drop cloths save a lot of cleanup time.
The reconfigured tunnel opening looks more true to the prototype location. The real tunnel is still accessible and is on a hiking trail above West Duluth. The plaster cloth does not stick to the foam sheets, but enough plaster was laid on the make it stay in place. Some cardboard strips and news paper were used to create new shapes on top of the foam sheets. It is important to check clearances for trains. One must also keep in mind that the next layer; the rock castings add a fair amount of thickness to these areas.
A few more shots of the newly hardshelled hill. There are a least two layers of plaster cloth and this is allowed to dry for several days before castings are added. In our case, the casting will come about a month later. We have found sources for remnants of plaster cloth on the Internet. It is sold in 20 pound lots for far less that the rolls at craft and hobby stores. The stuff is good, but can be a bit ragged. Scott like to brush a layer of plaster onto the plaster cloth surface to add a little more strength and so the surface does not weaken when wet castings are applied.
We only made one trip in April, so not as much progress was made as most months when we make two trips to the project site. Lots of smaller things were done such as wiring in an auto reverse module for the Millhouse River turntable at West Duluth yard. A Digitrax unit is used and works great. We no longer need to throw a DPDT switch when a loco is turned.
The Fallen Barn was finished and installed in place. The shingles and debris add
a lot to the kit which is made by Laser-
The two photos above demonstrate one technique used to camouflage the optical detection
sensors used to activate the crossing signals further down the line. The photo on
the left shows the location of the two sensors; Infrared LED is on the right side
of the track and the phototransistor is on the left side. The phototransistor is
hidden behind a short section of fence with bushes and debris to help hide it. The
infrared LED is inside a rusty barrel, see the close-
More detail has been added to the hobo camp, including more foliage, a rusted panel truck and a flickering campfire. Electronics for the campfire come from Evan’s designs and uses LEDs. I’ll post better photos of the campfire soon.
Our first work session in May resulted in finishing the rockwork around the tunnel on the hill. We also continued to put down ground cover and worked on new areas with hardshell. I forgot the compact flash card for my camera this trip and we could not find one locally to buy that my camera would recognize. So there are few photos, taken with a cell phone and the quality is not so great, but here are some images of the hill, etc. I’ll take more shots next trip.
The first task is casting the rock faces in molding plaster. Scott prefers molding plaster over Hydrocal as it takes color better., but is still much harder than plaster of Paris. John and Scott spent one entire day casting the rocks from numerous different molds. Some carving is also done to blend the differing casting into one another. We are aiming for a basalt structure with lots of vertical uplift and fracturing.
The casting dried sufficiently overnight to allow the coloring process to begin. Diluted artist acrylic paints are “slopped” over the castings. Scott works with few colors: Raw Sienna, Burnt Sienna & Burnt Umber are the three base colors. They are applied randomly and a spray bottle of clear water is used to keep the colors wet and moving while being brushed on the rocks. Some raw plaster is allowed to remain through this process.
The big changes appear when a layer of diluted black acrylic paint is brushed over the preceding three colors and worked into all the detail and crevasses. Again, clear water is sprayed to keep the black tint moving. The result at this point can be rather dark and not so nice to look at, but there is more work to be done that changes all that. Once the black wash is dry all of the previously used colors plus white and Gray are squeezed from the tube onto a pallet. All of these colors are dry brushed onto the rock surface to blend and highlight. While the rocks in the real life location we are modeling are predominately Gray, there is always some variation of color and this is the look we are going for. We want some hints of brown and tan as well as a little redish hue here and there.
Once the colors are satisfactory ground cover can be added. This step really make the previous work “pop”.
This over view shows a variety of colors and textures in the ground cover. Most of the ground foam is from Timberline Scenery.
Pleas excuse the fuzziness of the photos. While the phone camera is pretty good, it lacks depth of field. Two final shots of the finished rock and surrounding scenery. There are still scores of trees to add to this area so there will be more photos to come.


Would you like your company name on your badges?
Will anyone in your group require special accommodations?


|
Zapatec Tree | ||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
| SUMMARY: FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
Object | +--Zapatec.Tree
| Nested Class Summary | |
<static class> |
Zapatec.Tree.Node |
| Field Summary | |
<static> Object |
Utils
Utils class with some commonly used small methods |
| Method Summary | |
Object
|
appendChild(newChild, parent, atStart)
Append a child to the start or end of the given parent. |
void
|
collapseAll()
Call this function to collapse all items in the tree. |
void
|
collapseToLevel(level)
Collapses the tree up to the given level. |
void
|
discard(leaveDOM)
Destroy this instance. |
void
|
expandAll()
Call this function to expand all items in the tree. |
void
|
expandToLevel(level)
Expands tree up to given level. |
Object
|
find(findFunc)
Finds first node in a tree where findFunc returns true |
Object
|
findAll(findFunc)
Finds all nodes in a tree where findFunc returns true |
Object
|
getNode(id, <boolean> omitWarning)
Get node by its ID |
Object
|
getParent(id, mode)
Call to get the parent to append, insert or remove a child either at start or end position or in between two nodes of the (sub-)tree. |
Object
|
getState()
Returns JSON with current tree state. |
Object
|
insertAfter(newChild, refChild)
A new child can be inserted after some nodes. |
Object
|
insertBefore(newChild, refChild)
A new child can be inserted before some node. |
Object
|
loadDataHtml(objSource)
\internal Function to load tree content on tree load from HTML element |
Object
|
makeNode(html, type)
|
void
|
onItemSelect()
|
void
|
reconfigure(<object> objArgs)
Reconfigures the tree with new config options after it was initialized. |
Object
|
removeChild(oldChild)
Remove child in the tree. |
void
|
sync(itemId)
Synchronize tree to given node. |
void
|
toggleAll()
Call this function to toggle all items in the tree. |
void
|
toggleItem(nodeId, state)
You can expand, collapse or toggle a specific item |
| Field Detail |
<static> Object Utils
| Method Detail |
Object appendChild(newChild, parent, atStart)
newChild
- {object} reference to an HTML element created of type LI or JSON object with data.
parent
- {object} ID of parent node where new child will be added. If null - add to top level.
atStart
- {boolean} optional. If true if the child going to be added at the start of the parent.
void collapseAll()
void collapseToLevel(level)
level
- {int} level to collapse.
void discard(leaveDOM)
leaveDOM
- {boolean} If true - DOM tree will be preserved
void expandAll()
void expandToLevel(level)
level
- {int} level to expand.
Object find(findFunc)
search
- criterion
Object findAll(findFunc)
search
- criterion
Object getNode(id, <boolean> omitWarning)
omitWarning
- If true - do not show error message
ID
-
Object getParent(id, mode)
id
- {String} -- id of the parent the new child will be added to or inserted before/at.
mode
- {String} -- "I" is for inserting a child node.
Object getState()
Object insertAfter(newChild, refChild)
newChild
- {object} New child node to be inserted into the tree. HTML element or JSON object.
refChild
- {object} ID of the child node which the new child node will be inserted after.
Object insertBefore(newChild, refChild)
newChild
- {object} New child node to be inserted into the tree. HTML element or JSON object.
refChild
- {object} ID of the child node which the new child node will be inserted before
Object loadDataHtml(objSource)
objResponse
- {Object} Server response Format description: Common HTML list -

...
...

Object makeNode(html, type)
html
- {String} html of the node; may include
,
 elements; user is responsible for the content of the html.
type
- {String} type of the node to be created
void onItemSelect()
void reconfigure(<object> objArgs)
objArgs
- Changes to user configuration
Object removeChild(oldChild)
ID
- of node.
void sync(itemId)
node
- ID
void toggleAll()
void toggleItem(nodeId, state)
nodeId
- {string} node ID.
state
- {boolean} If true - expand node, false - collapse, null - toggle
|
Zapatec Tree | ||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
| SUMMARY: FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |


Rashel's Portfolio
Hi! My name is Rashel Rojas and I am first-generation student majoring in computer science at Columbia University. What got me into CS was a beginner's JavaScript class in middle school and it became something that I am passionate about. I hope to use my skills in CS to eventually work at a company working on environmental and sustainability projects.
A little about me: I'm Ecuadorian, I love working out, and I am so excited to a part of SPS!
Click here to read a fun fact about me or click the button below.


Join our community
30-days, hassie-free money back guarantee
Gain access to our full library of tutorials along with expert code reviews.
Perfect for any developers whoare seriois about honing their skills
Why Us
Tutorials by industry experts Peer & expert code review Coding exercises Access to our GitHub repos Community forum Flashcard decks New videos every week


In this sublesson, we will walk through the CloudFormation template that launches the static website solution. We'll cover some of the basics of CloudFormation while reviewing the AWS resources that are provisioned as part of this solution. A link to the CloudFormation template is provided below.
The pipeline.yml provisions the following AWS resources in its CloudFormation template are:
In addition, the pipeline.yml makes a call to a CloudFormation template provided by AWS that provisons EC2 instance(s) and installs the CodeDeploy on these instances. This template provisions the following AWS resources:


runtime.m.park (field)
14 uses
runtime (current package)
proc.go#L1186: notewakeup(&mp.park)
proc.go#L1340: notesleep(&g.m.park)
proc.go#L1341: noteclear(&g.m.park)
proc.go#L1631: notewakeup(&mp.park)
proc.go#L2353: notewakeup(&nmp.park)
proc.go#L2479: notewakeup(&mp.park)
proc.go#L5072: notewakeup(&mp.park)
runtime2.go#L524: park note
rwmutex.go#L54: notesleep(&m.park)
rwmutex.go#L55: noteclear(&m.park)
rwmutex.go#L73: notewakeup(&w.park)
rwmutex.go#L95: notesleep(&m.park)
rwmutex.go#L96: noteclear(&m.park)
rwmutex.go#L116: notewakeup(&reader.park)
The pages are generated with Golds v0.2.7-preview. (GOOS=darwin GOARCH=amd64)


@(idqid: String, idqemail: String, responseCode: Option[String], description: Option[String])
User ID: @idqid
Email: @idqemail
Response Code: @responseCode
Description: @description


This site won't work unless you put in page code
This: akahusky24.github.io/SchoolFiles/Hidden/View?q=PAGECODE
I put page code on this site, to ensure the site is secure the page codes are encoded for even more secured site.


Stopping Messi has become Real Madrid coach Zidane's obsession
by sport.es- The Argentine has hit top gear after an injury-hit start to the campaign
With just nine days to go until the Clasico between Barcelona and Real Madrid at Camp Nou, Zinedine Zidane has become obsessed with how to stop Lionel Messi.
Messi has become a nightmare for any rival to deal with. Madrid are no different. With the first Clasico of the season on Dec. 18, Zidane has been dedicating large chunks of time to studying how to stop the Argentine.
Barça's No.10 has returned to top form recently after an injury-hit start to the season -- scoring three against Mallorca and the winner against Atletico Madrid.
Until now, opponents have tried everything, but Messi has always won. Especially when it comes to the Clasico, one of his favourite games. He's always motivated and, as revealed in AS on Monday, Madrid are aware that stopping him could hold the key to the game.
Zidane doesn't want any more Messi surprises. Therefore, he's looking at what he can do to slow him down. Man marking? That could be a job for Fede Valverde, who's been one of Los Blancos' best players this season.
Another option would be to turn to the centre-backs, as has been the case previously. Varane and Sergio Ramos would be tasked with controlling the Argentine's movements.
Finally, Casemiro, who's a booking away from a ban with a tricky trip to Valencia to come first, could be another option.
For now, Zidane's weighing up the alternatives, man-marking or zonal, but he's aware that whatever he does, stopping Messi is almost mission impossible.


Hello, my name is Kiran. Thank you for browsing my online portfolio and resume. This website contains information about some of my projects, my work experiences, and my education. I graduated with a Masters degree in Computer Engineering from the University of California, Riverside. I'm an Experienced Infrastructure Specialist with a demonstrated history of working in the insurance industry. Skilled in Enterprise Content Management, Linux Administration, Microsoft Windows Administration, Web and Mobile App Development. I also worked as a UI Developer at Sanjeevani Labs, Hyderabad, India where I was involved in Front-End Web development. During my undergrad, I have also successfully led my team in designing, developing, and completing two extensive web applications. I have experience coding in a couple of programming languages and various Front End technologies. I plan to broaden my knowledge in this field over time.
Along with having strong interpersonal skills, I am a quick learner and known to effectively plan out and complete project tasks in a timely manner. I have a sincere passion for learning new things and applying my knowledge to even more cool projects!
.


Corporate Hands | GraceKennedy gives Sunbeam Children’s Home a facelift 14 Nov 2019, 05:20 Karen Willis-Mussington, senior brand manager, GraceKennedy, and her fellow colleague in action painting the recreational space at the Sunbeam Children’s Home.Contributed


###LISTS The official department reading lists for M&E (as of 2013)
Plato, Meno; Phaedo; Republic, Books V-VII; Parmenides 127-135;
Theaetetus; Timaeus 27-52
Aristotle, Categories, Chaps. 1-5; Posterior Analytics I.1-3, II.19; Physics I.7,
II.1-3, 7-9, IV.10-14; De Anima, Books II and III; Metaphysics I.1-4, 6, 9,
IV.1-2, VI.1, VII.1-6, 13-17, VIII.1-2, XII.6-10
Epicurus, Letter to Herodotus
Diogenes Laertius, Lives VII.45-54, 132-59 (on Stoics)
Sextus Empiricus, Outlines of Pyrrhonism I.1-13
Plotinus, Enneads I.6, V.1, and VI.9
Porphyry, Isagoge
Augustine, On the Free Choice of the Will, Book II; Confessions VII, VIII.5, 8-10,
XI.14-28; City of God, VIII.1-12, XII.1-9; Against the Academics II. 11-13,
III.1-8
Boethius, Commentary on Isagoge I.10-11 (on universals); Consolation of
Philosophy V.2, 3, 6 (on eternity and foreknowledge)
Anselm, Proslogion + debate between Gaunilo and Anselm
Abelard, Glosses on Porphyry (on universals)
Aquinas, Summa Theologica I, Questions 2, 12-14, 19
William of Ockham, Summa Logicae Part I, Chaps. 14-17
Descartes, Meditations
Leibniz, Discourse on Metaphysics; Monadology; “Primary Truths” and “A New
System of Nature”
Spinoza, Ethics, Parts I-II
Locke, An Essay Concerning Human Understanding I.1, II. 1-12, 21, 23, 27, III.2-
4, 6, IV.1-4, 6, 9-11
Berkeley, Principles of Human Knowledge
Hume, An Enquiry concerning Human Understanding; Treatise of Human Nature
I.4.6 (“Of Personal Identity”) and Appendix (on belief)
Kant, selections from Critique of Pure Reason: “Preface to the Second Edition”;
“Introduction”; “Transcendental Aesthetic”; “Transcendental Analytic”
(incl. “Analytic of Concepts” and “Analytic of Principles”); “Transcendental
Dialectic,” Introduction and Book II, Chap. 2 (The Antinomy of Pure
Reason”); “The Paralogisms of Pure Reason”
Hegel, Phenomenology of Spirit, Chapter Four, Pt. A (“Independence and
Dependence of Self-Consciousness”); Encyclopedia (Introduction); The
Philosophy of History (Introduction); Lectures on the History of
Philosophy, Volume Three, Section Three, Part E (“The Final Result”)Nietzsche, Twilight of the Idols
Please let me know if you have the most recent list. Thanks.


Sometimes I feel the fear of
uncertainty stinging clear
And I can't help but ask myself how much
I'll let the fear take the wheel and steer
It's driven me before, and it seems to have a vague
Haunting mass appeal
Lately I'm beginning to find that I
should be the one behind the wheel
Whatever tomorrow brings, I'll be there
With open arms and open eyes, yeah
Whatever tomorrow brings, I'll be there, I'll be there
So if I decide to waiver my
chance to be one of the hive
Will I choose water over wine and
hold my own and drive, oh oh
It's driven me before, and it seems to be the way
That everyone else gets around
Lately, I'm beginning to find that when I
drive myself, my light is found
Whatever tomorrow brings, I'll be there
With open arms and open eyes, yeah
Whatever tomorrow brings, I'll be there, I'll be there
Would you choose water over wine...
hold the wheel and drive?
Whatever tomorrow brings, I'll be there
With open arms and open eyes, yeah
Whatever tomorrow brings, I'll be there, I'll be there


Channel 4 threatens to 'empty-chair' Boris Johnson during climate change debate
by Scotsman ReporterThe Prime Minister could be "empty-chaired" during a televised climate change debate on Thursday.
Boris Johnson and Brexit Party leader Nigel Farage have yet to respond to a request to attend the hour-long Emergency On Planet Earth debate on Channel 4 News, which will focus solely on climate change.
The broadcaster said the debate will take place even if they are unable to take up the invitation.
Channel 4 has invited seven party leaders to the discussion, but so far only Labour leader Jeremy Corbyn, Scottish First Minister and SNP leader Nicola Sturgeon, Liberal Democrat leader
Jo Swinson and Green co-leader Sian Berry have accepted the invitation.
READ MORE - Which countries would be Scotland's closest allies after independence?
READ MORE - Climate change: Gas is on the way out. Here’s how we can still heat our homes – Andy Yuill
Ben de Pear, editor of Channel 4 News, said: "There is no more urgent issue facing the planet and we are delighted to open the whole of our programme for all the party leaders to show what plans they have to confront it."
Presenter Krishnan Guru-Murthy added: "It is a huge privilege to be hosting the people who want to run the country debating the most important issue in the world.
"How much do we need to change the way we live? Is it the end of fast fashion, fast cars, foreign holidays and red meat? Do any of them have a credible plan to cut our net emissions to zero?"
The debate will take place on Thursday at 7pm and will begin with a short opening statement from each leader.


assigned
by None at 2021-05-06 19:37:38.This is ready for review. I noticed that the remote storage is not added in the edit view but I don't think it is needed since we said that moving forward we are not going to do any edits on the holding locations table using the UI.
Ok I turned this PR to draft. @kevinreiss noticed that some remote_storage values for mendel are missing.
PR is updated.
head_ref_force_pushed
by Christina Chortaria at 2021-05-06 14:09:24.ready_for_review
by Christina Chortaria at 2021-05-06 14:09:46.convert_to_draft
by Christina Chortaria at 2021-05-06 14:14:15.head_ref_force_pushed
by Christina Chortaria at 2021-05-06 16:08:47.ready_for_review
by Christina Chortaria at 2021-05-06 16:09:39.deployed
by Trey Pendragon at 2021-05-06 16:43:52.convert_to_draft
by Christina Chortaria at 2021-05-06 16:58:43.mentioned
by Kevin Reiss at 2021-05-06 16:59:39.subscribed
by Kevin Reiss at 2021-05-06 16:59:39.head_ref_force_pushed
by Christina Chortaria at 2021-05-06 17:21:10.deployed
by Trey Pendragon at 2021-05-06 17:36:00.ready_for_review
by Christina Chortaria at 2021-05-06 17:38:51.renamed
by Christina Chortaria at 2021-05-06 17:39:32.referenced
by Christina Chortaria at 2021-05-06 18:42:07.merged
by Christina Chortaria at 2021-05-06 18:42:08.closed
by Christina Chortaria at 2021-05-06 18:42:08.head_ref_deleted
by Christina Chortaria at 2021-05-06 18:42:08.deployed
by Trey Pendragon at 2021-05-06 16:20:03.We need to specify this feature for the case where there are multiple items, some are on CDL and some which aren't.
We need to specify behavior for the search results page and the show page. For the show page we would like to replicate current functionality. For the search results page since the logic has been simplified there's not a clear analogue.
head_ref_force_pushed
by Eliot Jordan at 2021-05-06 20:25:54.head_ref_force_pushed
by Eliot Jordan at 2021-05-06 20:38:23.head_ref_force_pushed
by Eliot Jordan at 2021-05-06 21:01:22.ready_for_review
by Hector Correa at 2021-05-06 21:01:13.labeled
by Kim Leaman at 2021-05-06 19:17:09.labeled
by Kim Leaman at 2021-05-06 19:17:09.mentioned
by Shaun Ellis at 2021-05-06 19:17:10.subscribed
by Shaun Ellis at 2021-05-06 19:17:10.mentioned
by Trey Pendragon at 2021-05-06 19:17:10.subscribed
by Trey Pendragon at 2021-05-06 19:17:10.renamed
by Kim Leaman at 2021-05-06 19:21:06.assigned
by Kevin McElwee at 2021-05-06 02:03:26.This is done in the vireo_transformation
code:
labeled
by None at 2021-05-06 21:57:30.labeled
by None at 2021-05-06 21:57:30.labeled
by None at 2021-05-06 21:59:54.labeled
by None at 2021-05-06 21:59:55.referenced
by Trey Pendragon at 2021-05-05 22:53:14.closed
by James R. Griffin III at 2021-05-06 15:35:10.referenced
by James R. Griffin III at 2021-05-06 15:35:10.merged
by James R. Griffin III at 2021-05-06 15:35:10.closed
by James R. Griffin III at 2021-05-06 15:35:10.head_ref_deleted
by James R. Griffin III at 2021-05-06 15:35:16.referenced
by Trey Pendragon at 2021-05-06 16:42:13.merged
by Trey Pendragon at 2021-05-06 16:42:13.closed
by Trey Pendragon at 2021-05-06 16:42:14.head_ref_deleted
by Trey Pendragon at 2021-05-06 16:42:16.labeled
by Trey Pendragon at 2021-05-06 17:04:37.labeled
by Trey Pendragon at 2021-05-06 17:04:39.assigned
by Trey Pendragon at 2021-05-06 17:04:45.closed
by Trey Pendragon at 2021-05-06 18:00:09.head_ref_force_pushed
by Trey Pendragon at 2021-05-06 17:56:56.referenced
by Trey Pendragon at 2021-05-06 18:00:09.merged
by Trey Pendragon at 2021-05-06 18:00:09.closed
by Trey Pendragon at 2021-05-06 18:00:09.head_ref_deleted
by Trey Pendragon at 2021-05-06 18:00:11.referenced
by James R. Griffin III at 2021-05-06 18:39:24.merged
by James R. Griffin III at 2021-05-06 18:39:24.closed
by James R. Griffin III at 2021-05-06 18:39:24.head_ref_deleted
by James R. Griffin III at 2021-05-06 18:39:28.closed
by None at 2021-05-06 12:56:49.referenced
by None at 2021-05-06 12:56:49.merged
by None at 2021-05-06 12:56:49.closed
by None at 2021-05-06 12:56:50.head_ref_deleted
by None at 2021-05-06 12:56:55.Fixed!
closed
by Bess Sadler at 2021-05-06 20:40:09.assigned
by Bess Sadler at 2021-05-06 20:41:58.referenced
by Christina Chortaria at 2021-05-06 17:14:34.merged
by Christina Chortaria at 2021-05-06 17:14:34.closed
by Christina Chortaria at 2021-05-06 17:14:34.head_ref_deleted
by Christina Chortaria at 2021-05-06 17:14:35.@carolyncole I fixed a couple of things; maybe you could have another look when you get a chance?
mentioned
by None at 2021-05-06 12:54:51.subscribed
by None at 2021-05-06 12:54:51.referenced
by Francis Kayiwa at 2021-05-06 15:14:42.merged
by Francis Kayiwa at 2021-05-06 15:14:42.closed
by Francis Kayiwa at 2021-05-06 15:14:42.head_ref_deleted
by Francis Kayiwa at 2021-05-06 15:14:43.Received confirmation from stakeholders that we can retire this feature.
Updated link in left sidebar to take patrons to the catalog view for the two locations.
@kevinreiss Do we want to setup a redirect for /marquand/vault to go to that same catalog view?
To do:
mentioned
by Kevin Reiss at 2021-05-06 13:43:36.subscribed
by Kevin Reiss at 2021-05-06 13:43:36.review_requested
by Axa Mei Liauw at 2021-05-06 15:16:07.referenced
by Kevin Reiss at 2021-05-06 15:27:31.merged
by Kevin Reiss at 2021-05-06 15:27:31.closed
by Kevin Reiss at 2021-05-06 15:27:31.head_ref_deleted
by Kevin Reiss at 2021-05-06 15:27:31.closed
by Axa Mei Liauw at 2021-05-06 22:39:55.I attended the UV community call this morning and we agreed on a plan for how to fix this. They do not have anyone on staff at the moment who can work on it, but we are welcome to contribute a patch for v3. If we need any type of support, we may need to contribute to Open Collective.
@sdellis Is there documentation for the plan, or is the plan that we either work on it or contribute to Open Collective?
@tpendragon Ed has a long-term plan for v4, but that likely won't be done until 2022. The short-term plan is to collapse the index and thumbnails into a button on the bottom of the screen in responsive view. This would trigger a modal dialogue, similar to the Info Panel.
They don't have a developer to work on it, so we would need to pony up and contribute the patch if we want it done. If we need any of Ed's time for support/troubleshooting, we would need to pay for his time via Open Collective (or other arrangement).
mentioned
by Shaun Ellis at 2021-05-06 18:35:59.subscribed
by Shaun Ellis at 2021-05-06 18:35:59.mentioned
by Trey Pendragon at 2021-05-06 18:46:52.subscribed
by Trey Pendragon at 2021-05-06 18:46:52.renamed
by Kevin Reiss at 2021-05-06 13:26:35.renamed
by Kevin Reiss at 2021-05-06 13:26:43.head_ref_force_pushed
by Kevin Reiss at 2021-05-06 13:09:33.closed
by Kevin Reiss at 2021-05-06 14:02:19.review_requested
by Kevin Reiss at 2021-05-06 14:52:27.base_ref_changed
by Kevin Reiss at 2021-05-06 15:56:05.referenced
by Bess Sadler at 2021-05-06 12:47:39.merged
by Bess Sadler at 2021-05-06 12:47:39.closed
by Bess Sadler at 2021-05-06 12:47:40.head_ref_deleted
by Bess Sadler at 2021-05-06 12:47:40.Related issue - https://github.com/pulibrary/dspace-development/issues/294
This is done! :)
closed
by Bess Sadler at 2021-05-06 14:16:12.head_ref_force_pushed
by Bess Sadler at 2021-05-06 18:32:48.referenced
by James R. Griffin III at 2021-05-06 18:35:40.merged
by James R. Griffin III at 2021-05-06 18:35:40.closed
by James R. Griffin III at 2021-05-06 18:35:40.head_ref_deleted
by James R. Griffin III at 2021-05-06 18:35:40.labeled
by Bess Sadler at 2021-05-06 13:28:07.assigned
by Bess Sadler at 2021-05-06 13:28:07.closed
by James R. Griffin III at 2021-05-06 18:35:40.assigned
by Bess Sadler at 2021-05-06 13:28:20.referenced
by James R. Griffin III at 2021-05-06 20:38:19.merged
by James R. Griffin III at 2021-05-06 20:38:19.closed
by James R. Griffin III at 2021-05-06 20:38:19.head_ref_deleted
by James R. Griffin III at 2021-05-06 20:38:20.


---
layout: page
title: Welcome
use-site-title: true
---
This is a webpage created as part of the assesment for "Programming for the Social Sciences".
On the top right, there are links to the relevant sections of the site:
- About - presents some information about me.
- Blog - the blog section of the website, with a sample blogpost
- Agent Based Model - gives a brief description of the agent based model implemented in the practicals and links to the code
- Mapper - gives a brief description of the Mapper algorithm and the implementation of it. This is the second assignment.
This website uses the beutiful-jerkyl template.
All pages except this one are written in markdown. This page is pure HTML.