My question here is about Google Classroom's API.
When i am in the Classwork tab, I have a button to make posts; one option is "material". This type is not an assignement and does not have an assigned grade. This is a perfect concept: I can add materials, sorted by topics to my classwork page with no grades or assignments needed.
The problem for me is when i go to the api and look for that functionality, you can only see courseWork objects with "ASSIGNMENT" "SHORT_ANSWER_QUESTION" and "MULTIPLE_CHOICE_QUESTION" workTypes. All of those type have grades related, but no option exists for the "MATERIAL" type I can choose from the Create menu.
Nor do Material objects seem to exist in the API call.
Many other objects exist that I can find: coursework, announcements, topics, students, courses, teachers and others, but no material's object. Is this an omission? There is a "material" available but it's used for the attachments IN a CourseWork item, not the CourseWork itself.
Jose- I think I asked the same question as you but might have been clearer with the details. Perhaps check here if answers start to roll in. I have spent hours trying to interrogate objects to find this info with no luck.
Google Classroom API Create Material
I would have added this as a comment but my reputation doesn't allow it.
UPDATE: Huge thanks to #ziganotschka for this:
Indeed, there is a feature request for it already:
https://issuetracker.google.com/issues/127591179
I suggest you to give it a star to increase visibility and get updates
on the implementation status of the feature.
Related
I'm having a problem with Rasa_NLU giving me the wrong entity for an intent. An example is “How do I get to New York?” Where, I tagged the training data to name the entity “city”. In a different intent, it was tagged “destination”.
intent: check_weather
what is the weather in new york?
intent: get_directions
how do I get to new york?
I have a script that takes action on the intent returned and processes the entities. If I get back the get_directions intent, I’ll look in the json for the destination entity, but it has city instead. Using ner_crf, is there a way to de-emphasize entities in an intent, so that the classifier is biased to those that the intent was trained for? That is, the classifier would be weighted to giving a destination for get_directions, and a city for get_weather?
The typical answer I've found is to add more training examples. I'm up to 60 for each of the two intents I have, and it is still getting it wrong.
As of right now, you can only featurize/unfeaturize all entities for a certain intent. I can see that that's not really your use case since both intents require entities -- just different ones. There is currently a community PR open to add per-intent featurization of specific entities, so it will be available in the future.
Im using Eventbrites api to get information about events. I cant find any price information on the event, even though I can see price information if I check the events page at eventbrite site.
I can see from here that there is an optional property "ticket_availability", but its seems to be non-existing, even though I can see price info on the event´s eventbrite page)
Further down in the documentation its also mention something called "Ticket class", that should be an anonymous object, but I cant find it anywhere,
(and yes, I have contacted their dev support)
[Accepted answer, cant set it until tomorrow]
Answer from eventbrite:s dev support. If you see this: THANKS!(again) :D
Ticket Classes are the object that we use to represent the prices of an event.
I think this is the endpoint you're looking for:
GET /v3/event/[EVENT ID]/ticket_classes/
https://www.eventbrite.com/developer/v3/endpoints/events/#ebapi-get-events-id-ticket-classes
That will return a list of Ticket Class objects (since events can have more than one price). Here's the documentation on the Ticket Class object it self. The cost field is what you are likely interested in.
I ran into this issue and it turns out ticket_availability is an expansion field for the event endpoints, so you have to request it specifically.
For example, this request:
https://www.eventbriteapi.com/v3/venues/28582043/events/
Would need to become:
https://www.eventbriteapi.com/v3/venues/28582043/events/?expand=ticket_availability
This section of the documentation explains expansions: https://www.eventbrite.com/platform/api#/introduction/expansions
At the top of the documentation for Events you can see the list of expansions that are available for event endpoints: https://www.eventbrite.com/platform/api#/reference/event
ticket_availability doesn't contain the full data on the tickets, so using Ticket Classes as the other answer mentions is the way to go if you need a lot of information about tickets for a particular event. For example:
https://www.eventbriteapi.com/v3/events/216395423537/ticket_classes/for_sale/
I find that the nickname and reference_id fields work differently across platforms and I'd like to get clarification on how they should be used.
With the API, I can retrieve and set both these fields.
In the web-based dashboard, both fields are displayed and can be edited if present, but there's no way to enter a nickname when creating a new customer.
In the Register iOS app, none of these fields are shown or editable. They're also absent when creating a new customer.
What I want to do is map Square Customers to our existing members, but we're facing three problems:
reference_id seems to map perfectly with our existing member numbers but, as mentioned, it's nowhere to be seen in the Register app.
Searching customers in the Register app only searches in names and emails. It would really help us if it searched in reference_id as well.
CustomerGroupInfo is read-only via the API (and not even an endpoint). We would map these to our membership levels.
As of now, I'm looking at ugly workarounds, but I wanted to know if something in the roadmap could help us out. Thanks in advance to the people at Square!
I've looked through numerous answers (most were slightly outdated), and I was wondering if Apple had some sort of way to identify the type of business it queried?
From the reference guide, MKMapItem has 5 variables, none of which tell me a place is a "Thai Restaurant" or something like that.
placemark
isCurrentLocation
name
phoneNumber
url
I think its interesting how when you do a MKMapkit query on "thai", it'll give you a list of thai restaurants but thats a one way street and no where later can I take a result from the query on "thai" to verify that it is indeed a "thai" restaurant. More importantly, what I am particularly interested in is if a business is a "Thai" restaurant and a "Bar" as well, I want to be able to do a MKMapKit query on "Bar" OR "Thai" and be able to get both of those tags
I can see a solution of getting the coordinates of a business then using Google Maps API or even Yelp API and doing a search on there to get the "type of business" but that seems extremely cumbersome and inefficient.
Thanks for any advice! One of my first questions so please so easy on me =)
First, take a look with this link : http://www.raywenderlich.com/13160/using-the-google-places-api-with-mapkit
The google API will send back the name, type, location of business location near you.
It's also send icons(via image link) of business location, so you can display it on the map, which can help you which is market, which is coffeeshop...
But the "Thai Restaurant" maybe too detail so google doesn't want to show it.
Sorry about my bad english.
Hope it help.
For that you should use google near by place search or place search api. you can pass thailand as place name and restaurant to type and it will return you all the restaurant in thailand.
I've added several Subjects under the Admin section of Dynamics CRM. I'd really like to add one of these "Subjects" to the Regarding field within an Activity. E.g. someone called, and it was related to "ProductX".
Strangely, the entity type "Subject" does not appear when trying to select an item for the field. A range of other entity types such as "Contacts" and "Accounts" appear.
Does anyone know why Subjects can't be selected here? I would have expected this was OOB functionality.
That because it doesn’t really make sense to have activities regarding a subject.
An activity only really makes sense in the context of something else, and that something else is generally a real thing in the world or a piece of work. The Regarding field really says: "This Activity involves working on this thing".
For example, if John Smith rings your company, it makes sense to create a new Phone Call activity that Regards the Contact record of John Smith. With this approach you can see the entire activity history against a Contact. By making the Phone Call regard the Contact you are saying this piece of work is about the Contact.
If the Phone Call was Regarding a Subject, it would be saying, "This Phone Call involves working on the Subject", which isn’t true, its work about the Contact. Also you lose the ability to track correspondence with the contact.
So my suggestion would be, use the Regarding field to link to people and things, and add a relationship between your activities and subject if you want to classify your phone calls.
As a side, there is a product entity in CRM (it can’t be Regarding however), so perhaps you should create a relationship to that.