Methods for retrieving content Sample Clauses

The "Methods for retrieving content" clause defines the procedures and mechanisms by which users or parties can access or obtain specific content covered by the agreement. This may include specifying whether content is available through downloads, streaming, physical delivery, or via a secure portal, and may outline any authentication or technical requirements needed for access. By clearly establishing how content can be retrieved, this clause ensures both parties understand the process, reducing confusion and disputes regarding content delivery and access rights.
Methods for retrieving content. ‌ The available methods to retrieve content from Blogger were described in the previous section. In this section we summarise the methods that are useful for the purposes of the project. Given a set of keywords extracted from policies or defined by policy makers and a list of blog URLs one can first search the Posts in Blogger, through the search method. After gathering the related content and obtaining the ID of each returned Post, the method list can be used to retrieve the comments on this post. Searching the posts and listing the available comments also returns the id of the authors both of the post and the comments. Given these userIds information about the users can also be obtained through the get method for the user resource. An overview of methods that will be used to obtain appropriate data is presented in Table 3: Blogger API methods for retrieving content getByUrl Blog url string NO The url of the blog to retrieve. The method retrieves the blog that corresponds to the given url. Id, name, description, published, updated,url, posts, locale search Post blogId string NO The ID of the blog whose posts will be searched. The method searches the Blogger posts of a particular Blog for a certain query string and returns up to a maximum number of results. If the number of results is more than that then a pageToken is also returned that can be used to go through the next page of results in the next search request. id, published, datetime, title, content, author, location q string NO Full-text search query string. pageToken string YES The continuation token, used to page through large result sets. list Comments blogId string NO The ID of the blog. Given a blog and a post ID the method lists all the comments up to a number of results specified by maxResults, that have been posted regarding this blog post. If the number of comments is more than 20 Id, published, updated, content, author postId string NO The ID of the blog post to get comments for. maxResults unsigned integer YES The maximum number of activities to include in the response, used for paging. Acceptable values are 1 to 20, inclusive. (Default: 10) (the maximum value for maxResults) then a pageToken is also returned that can be used to go through the next page of results in the next list request. The erliest and latest dates of the comments to be fetch can also be specified. pageToken string YES The continuation token, used to page through large result sets. endDate datetime YES The latest date o...
View SourceView Similar (2)
Methods for retrieving content. ‌ The most useful Twitter method for our project is Search tweets, since it enables the NOMAD application to search and return all Twitter messages, where a keyword is mentioned. It provides also the capability to narrow search results coming from users from a specific location or written in a specific language. This can be vary valuable for the policy maker who wants to find out what people say in Twitter regarding a policy in a specific country or region during a given time interval. Furthermore, Get user timeline can be utilised to retrieve tweets from a particular Twitter account that is of NOMAD’s interest. 8▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇.▇▇▇/docs Get user timeline Tweets user_id String YES The ID of the user for whom to return results for. Helpful for disambiguating when a valid user ID is also a valid screen name. Access token, Read permission Returns a collection of the most recent Tweets posted by the user indicated by the screen_name or user_id parameters. This method can only return up to 3,200 of a user's most recent Tweets. Native retweets of other statuses by the user is included in this total, id_str, retweet_count, text, user Always specify either a user_id or screen_name when requesting a user timeline. screen_n ame String YES The screen name of the user for whom to return results for. Helpful for disambiguating when a valid screen name is also a user ID. Access token, Read permission Always specify either a user_id or screen_name when requesting a user timeline. since_id Integer YES Returns results with an ID greater than (that is, Access token, Read more recent than) the specified ID. There are limits to the number of Tweets which can be accessed through the API. If the limit of Tweets has occurred since the since_id, the since_id will be forced to the oldest ID available. permission regardless of whether include_rts is set to false when requesting this resource. ▇▇▇▇▇://▇▇▇.▇▇▇ ▇▇▇▇.▇▇▇/▇▇▇▇/ api/1.1/get/sta tuses/user_tim eline count ▇▇▇▇▇▇▇ YES Specifies the number of tweets to try and retrieve, up to a maximum of 200 per distinct request. The value of count is best thought of as a limit to the number of tweets to return because suspended or deleted content is removed after the count has been applied. We include retweets in the count, even if include_rts is not supplied. It is recommended you always send include_rts=1 when using this API method. Access token, Read permission max_id Integer YES Returns results with an ID less than (that is, older...
View Source
Methods for retrieving content. ‌ In this section we summarise the methods for retrieving content from Facebook that are useful for the purposes of the project. Thus, comments on the various Facebook resources (Status messages, Photos, Videos, etc.) can be extracted with the get comments methods analysed below. As shown in the Table 7: Facebook API Methods for retrieving content, these methods can as well return the id of user created this comment (form parameter). Given this id, information about the people who have created the relevant content can be accessed through the get methods on user resource. 1. So, to get insights from these or other pages devoted to a policy topic the homonymous method is going to be used. Finally, through the search method and given a set of keywords, one can search over the social graph on a set of keywords from policy models or domain models authored by policy makers. Get comments comments id String YES The Facebook ID of the access_token Id, from, comment All these fields are returned by default from an API call. If someone wants only some of them, he can use the parameters to restrict the result. message, created_time, likes, user_likes, type from String YES The user that created the comment access_token message String YES The comment text access_token ▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/docs/ref erence/api/status/ created_time String YES The datetime the comment was created access_token likes String YES The number of times this comment was liked access_token user_likes String YES This field is returned only if the authenticated user likes this comment access_token type String YES The type of this object; always returns comment access_token Get likes likes id String YES The Facebook ID of the access_token All these fields are returned by default Id, name person who made the like from an API call. If someone wants only some of them, he can use the parameters to restrict the result. ▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/docs/ref name String YES The Facebook name of the person who made the like access_token erence/api/status/
View Source
Methods for retrieving content. ‌ As already mentioned, among the available YouTube resources, only comments can be processed by NOMAD. However what is needed to trigger this process is to find out all videos that are in a particular category or that are associated with a particular keyword related with the policy under examination. This is evitable throuth the method Browsing with Categories and Keywords. After listing these videos, the associated comments are accessible through the method Retrieve comments. Then NOMAD can use Retrieve user profiles to gather data about users who have contributed to content. 9 ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇.▇▇▇/youtube/2.0/developers_guide_protocol_audience ge 50 of 87 Browsing with Videos Category String YES The category of videos Developer key, retrieve a feed of all of the videos that are videos Categories and the user is interested in. Either category or tag must be specified. access token in a particular category or that are associated with a particular keyword. (YouTube uses the term "tag" to identify a keyword relevant to a video.) ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇.▇▇▇/youtube/2 .0/developers_guide_protocol_category_k eyword_browsing Tag String YES The tag of videos. Either category or tag must be specified. Developer key, access token Retrieving data for single Videos videoid String NO P The video ID for a video is identified in feed entries by the <yt:videoid> tag. This tag appears in video feed entries – including standard feeds, search results, user-uploaded video feeds, etc. – as well as in favorite video feed entries, playlist feed entries, inbox feed entries and several types a of activity feed entries. Developer key, access token retrieve information about a single video ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇.▇▇▇/youtube/2 .0/developers_guide_protocol_video_entr ies Id, Uploader_Id, viewCount, favourite_cou nt, numDislikes, numLikes Retrieve user profiles User userId String NO User’s unique id Developer key, access token allows you to retrieve user profiles ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇.▇▇▇/youtube/2 .0/developers_guide_protocol_profiles About me, age, gender, hometown, location, hobbies, occupation, relationship Retrieve comments Comments Video id String NO Video’s unique id Developer key, access token ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇.▇▇▇/youtube/2 .0/developers_guide_protocol_comments ?hl=en#Retrieve_comments Author, Content, published
View Source

Related to Methods for retrieving content

  • Customer Content As part of the Services provided under this Agreement, Customer Data will be stored and processed in the data center region specified in the applicable Ordering Document. Axway shall not access Customer Content except in response to support or technical issues where Customer provides Axway with prior Customer’s written authorization required to access such Customer Content. Axway is not responsible for unauthorized access, alteration, theft or destruction of Customer Content arising from Customer’s own or its authorized users’ actions or omissions in contravention of the Documentation. Customer’s ability to recover any lost data resulting from Axway’s misconduct is limited to restoration by Axway from the most recent back-up.

  • THIRD PARTY WEBSITES AND CONTENT The Website contains (or you may be sent through the Website or the Company Services) links to other websites ("Third Party Websites") as well as articles, photographs, text, graphics, pictures, designs, music, sound, video, information, applications, software and other content or items belonging to or originating from third parties (the "Third Party Content"). Such Third Party Websites and Third Party Content are not investigated, monitored or checked for accuracy, appropriateness, or completeness by us, and we are not responsible for any Third Party Websites accessed through the Website or any Third Party Content posted on, available through or installed from the Website, including the content, accuracy, offensiveness, opinions, reliability, privacy practices or other policies of or contained in the Third Party Websites or the Third Party Content. Inclusion of, linking to or permitting the use or installation of any Third Party Website or any Third Party Content does not imply approval or endorsement thereof by us. If you decide to leave the Website and access the Third Party Websites or to use or install any Third Party Content, you do so at your own risk and you should be aware that our terms and policies no longer govern. You should review the applicable terms and policies, including privacy and data gathering practices, of any website to which you navigate from the Website or relating to any applications you use or install from the Website. Any purchases you make through Third Party Websites will be through other websites and from other companies, and Company takes no responsibility whatsoever in relation to such purchases which are exclusively between you and the applicable third party. Company reserves the right but does not have the obligation to:

  • Customer Data 5.1 The Customer shall have sole responsibility for the legality, reliability, integrity, accuracy and quality of the Customer Data. The customer being a contractor of DSA Airport, the customer shall not own the rights, title and interest in and to the Data which belongs to DSA Airport. 5.2 The Supplier shall follow its archiving procedures for Customer Data as set out in its Back- Up Policy available at ▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇ or such other website address as may be notified to the Customer from time to time, as such document may be amended by the Supplier in its sole discretion from time to time. In the event of any loss or damage to Customer Data, the Customer's sole and exclusive remedy shall be for the Supplier to use reasonable commercial endeavours to restore the lost or damaged Customer Data from the latest back-up of such Customer Data maintained by the Supplier in accordance with the archiving procedure described in its Back-Up Policy. The Supplier shall not be responsible for any loss, destruction, alteration or disclosure of Customer Data caused by any third party (except those third parties subcontracted by the Supplier to perform services related to Customer Data maintenance and back-up). 5.3 The Supplier shall, in providing the Services, comply with its Privacy and Security Policy relating to the privacy and security of the Customer Data available at ▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇ or such other website address as may be notified to the Customer from time to time, as such document may be amended from time to time by the Supplier in its sole discretion. 5.4 If the Supplier processes any personal data on the Customer’s behalf when performing its obligations under this agreement, the parties record their intention that the Customer shall be the data controller and the Supplier shall be a data processor and in any such case: (a) the Customer acknowledges and agrees that the personal data may be transferred or stored outside the EEA or the country where the Customer and the Authorised Users are located in order to carry out the Services and the Supplier’s other obligations under this agreement; (b) the Customer shall ensure that the Customer is entitled to transfer the relevant personal data to the Supplier so that the Supplier may lawfully use, process and transfer the personal data in accordance with this agreement on the Customer's behalf; (c) the Customer shall ensure that the relevant third parties have been informed of, and have given their consent to, such use, processing, and transfer as required by all applicable data protection legislation; (d) the Supplier shall process the personal data only in accordance with the terms of this agreement and any lawful instructions reasonably given by the Customer from time to time; and (e) each party shall take appropriate technical and organisational measures against unauthorised or unlawful processing of the personal data or its accidental loss, destruction or damage.

  • Return of Customer Data Okta shall return Customer Data to Customer and, to the extent allowed by applicable law, delete Customer Data in accordance with the procedures and time periods specified in the Trust & Compliance Documentation, unless the retention of the data is requested from Okta according to mandatory statutory laws.

  • Contract Database Metadata Elements Title: Sayville Union Free School District and Sayville Union Free School Custodial and Maintenance Employees Unit, United Public Service Employees Union (UPSEU), Local 424 (2011) Employer Name: Sayville Union Free School District Union: Sayville Union Free School Custodial and Maintenance Employees Unit, United Public Service Employees Union (UPSEU) Local: 424 Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 6131 Unit Size: 55 Number of Pages: 24 For additional research information and assistance, please visit the Research page of the Catherwood website - ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇▇▇▇▇.▇▇▇/library/research/ For additional information on the ILR School - ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇▇▇▇▇.▇▇▇/ 55 People TABLE OF CONTENTS ARTICLE Page XXII ANNUAL LEAVE DAYS 14 XXV BREAKS 18 XXVI CIVIL SERVICE LAW ARTICLE SECTION 75 18 XXVIII DURATION 19 XIV EMERGENCY WORK 11 XXI FOUL WEATHER CLOTHING 14 XI GRIEVANCE PROCEDURE 9 XVI HIGHER JOB CLASSIFICATION 12 XVIII HOLIDAYS 13 XV HOLIDAY AND WEEKEND BUILDING CHECKS 12 V INSURANCE 4 X LAYOFF, DISPLACEMENT AND RECALL ORDER 8 VII MANAGEMENT RIGHTS 7 XXVII MISCELLANEOUS 19 XVII NOTICES OF PROMOTIONS 13 XIII OVERTIME 10 II PAYROLL DEDUCTIONS 1 III PERSONNEL FILES 2 XXIV PHYSICAL EXAMINATIONS 18 XXIII RETIREMENT 16 IX STRIKES AND LOCKOUTS 7 XIX VACATIONS 13 XX VISITATION 14 IV WAGES 3 VI WORKERS' COMPENSATION 6 XII WORKWEEK 10 VIII WRITTEN BOARD POLICY 8 APPENDIX A 20 4/20/2016 AGREEMENT made and entered into this day of November 2013 between the SAYVILLE UNION FREE SCHOOL DISTRICT (hereinafter referred to as the “District”) and United Public Service Employees Union, ▇▇▇▇ ▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇, ▇▇▇▇▇▇▇▇▇▇, N.Y. 11779 (hereinafter referred to as the “Union”).