Forum Replies Created
- Posts
Hello!
Please email info@smrfoundation.org to arrange a remote repair session via Team Viewer.
Regards,
Marc
Hello!
Thank you for the interest in NodeXL!
We do not enable bypassing API restrictions.
For many years now, the Twitter “Whitelisting” is no longer active. All public users of the API are equal.
Commercial data sources do have access to deeper data and can deliver longer periods of data in one query.
We believe that any account that has Twitter Premium that is accessed through NodeXL, should receive the higher rate limits associated with a Premium account.
Regards,
Marc
Please consider scheduling a discussion with our consultants – we can help you navigate large data sets through NodeXL most effectively!
Contact us via: info@smrfoundation.org
“OutOfMemoryException” – What does that mean?
If this message shows up, you have reached the memory storage limits of your machine.
How large a network can NodeXL handle?
NodeXL can manage different numbers of edges based on the available computer system resources. The following are rough estimates:
4 GB of RAM: SMALL networks only less than a few thousand edges
8 GB of RAM: MEDIUM networks of less than 10-15 thousand edges
16GB of RAM: LARGE networks of less than 80-100 thousand edges
32 GB of RAM: VERY LARGE networks of less than 200 thousand edgesHow to deal with a VERY LARGE NETWORK?
Network analysis can require large amounts of computing resources or require long periods of time to perform (or both!).
Reducing the number of metrics calculated is one way to speed up analysis of a very large network.
If you do not plan on using all the different types of “centrality” metrics, you may just want to skip creating them. To do this, modify the metrics selected in the NodeXL>Analysis>Graph Metrics dialog.
In many cases network data sets can be reduced in useful ways that retain many important features and insights.
In many networks it can be possible to count and then remove all “isolate” vertices (nodes with zero connections).
All “singleton” or “pendant” vertices can also be counted and removed (these are vertices with just one connection to the network).
All duplicated edges can be removed. Optionally, duplicate edges can be counted and removed and the count added to the remaining edge as a weight representing the number of removed edges.
To perform this operation, see: NodeXL>Data>Prepare Data> Count and Merge Duplicate Edges:
Hello,
Thank you for your interest in NodeXL!
We are experiencing this problem with other Office 365 users lately. Please follow these steps to activate the “Document Actions” pane:
Open Excel
Got to File->Options
In the “General” tab, under “User interface options”, select the second option “Optimize for compatibility”
Close Excel
Open NodeXL
For more details please refer to this URL: https://support.office.com/en-us/article/outlook-attachment-preview-failure-88020c8e-43ae-4582-9554-511fbaf0d138–
MarcNodeXL is adapting to the changes in the Facebook API.
The latest version of NodeXL Pro was updated to work with the previous Facebook API update. In that release we added a Facebook Fan Page importer for users who are the Administrator of their Page. This importer continues to deliver the same data as previous. However, if you are not the Admin of a page, you must use the non-Admin importer which no longer delivers the names of the authors of comments, any reaction details, or time stamps. The resulting data is useful for content analysis but lacks much in the way of “network” data since the data needed to create meaningful edges have been removed.
More recently, the Facebook API has changed again and the “Search” feature that allowed users to discover Facebook Fan Pages of interest has been removed.
Facebook has deprecated the Search API as of 4 of April
https://developers.facebook.com/…/facebook-api-platform-pr…/The bad news is that you may no longer “Search” for a Page using the NodeXL Pro Facebook Fan Page Importer.
The good news is that you may perform this search in a web browser and transfer each Page ID# to the search box to select your desired page.
More good news! There is now a new importer for the connections between Facebook Fan Pages.
Thank you for the interest in NodeXL.
Facebook’s API no longer enables access to the personal friends list.
Facebook Pages and Groups are accessible to a limited extent.
You may import network data from Facebook using the:
NodeXL Pro> Data> Import>Import from Facebook Page
NodeXL Pro> Data> Import>Import from Facebook Group
Importers
The recent changes to the Facebook API have broken some of the features of the NodeXL Facebook importers
https://developers.facebook.com/docs/graph-api/changelog
We are investigating and will release an updated version of the importers soon. It is not yet clear how much of previous functionality will be retained depending on what remains of the key API calls.
It looks like the Fan Pages are more affected than the Groups importer.
The Fan Page importer looks like it no longer providers userIDs or reactions.
Many of the “edges” NodeXL extracted from Facebook were based on these data elements. These edges will no longer be available due to the Facebook changes in the API.
We are exploring ways of expanding on the existing Facebook Fan Page to Fan Page network collector – which still looks like it is available.
Facebook is a commercial property and is not obliged to provide *an* data if it does not want to.
That said, these recent changes to reduce data access reduce the credibility and desirability of Facebook as a platform for many kinds of users.
I predict that a Premium Facebook “product” will soon emerge to sell back the data that we all contributed to Facebook for free.
The most recent changes to the Facebook API have broken the NodeXL importers for Fan Pages and Groups.
We will be repairing as best as possible these importers by updating to the new API and its restrictions. We expect a release next week that will restore any remaining functionality that the API provides.
Apologies for the interruption in service. We will restore this feature as best we can given the increasing restrictions imposed by Facebook. This is a trend displayed by most of the platforms to increasingly restrict access to their data.
Regards,
MarcHello!
Thank you for the interest in NodeXL!We would like to help repair your installation of NodeXL.
May we request that you install Team Viewer 13 and then email info@smrfoundation with the details (Machine ID# and Passcode) and the time we can connect to your system?
Regards,
Marc
The recent changes to the Facebook API have broken some of the features of the NodeXL Facebook importers
https://developers.facebook.com/docs/graph-api/changelog
We are investigating and will release an updated version of the importers soon. It is not yet clear how much of previous functionality will be retained depending on what remains of the key API calls.
Regards,
Marc
It is possible but it is also likely to be slow.
What are the limits of the Twitter data importers?
The use of NodeXL Pro Twitter data importers requires a twitter account. Before your first data import you need to authorize NodeXL by entering a token number which is automatically sent to you during the authorization process.
Moreover Twitter’s public free API has many limits. NodeXL Basic and Pro are both effected by these limits. Data is available only for 8-9 days. Queries cannot return more than 18,000 tweets.The follower network is further restricted: the rate at which queries about who follows who can be asked is low.
NodeXL Pro does not enable the collection of data beyond these limits. That said, NodeXL can process data from commercial data providers (like Crimson Hexagon or Radian6). While these are expensive options, they may be the only way to get historical data from Twitter.
Commercial services like Radian6 and Crimson Hexagon provide archival data – but not cheaply!
You may be able to get a little bit more data from the public Twitter API by using the SINCE: and UNTIL: operators – example:QUERYTERM since:2016-01-21 until:2016-01-27. Since: and Until: operators scope the time frame of the query.
Twitter controls its API and throttles it based on unknowable parameters. We notice that the more the volume of tweets == less tweets delivered. One alternative is to do day long slices and append them in order to maximize the data available from Twitter.
You may also be interested in th Connected Action Graph Server Importer which enables NodeXL to connect to the “STREAM” API from Twitter (which sometimes delivers larger volumes of data).
Twitter applies additional limits to the Follows and Followers data query — it is “throttled” to a slower rate of data delivery than the other “Tweet” based queries.
If you are patient it may be possible to do this collection. That said, it is often the case that one or two users in a list of followers are celebrities who have very large numbers of followers. It is not practical to collect many tens of thousands of followers in a desktop application. Millions are not viable at all. NodeXL Pro offers the ability to set an upper threshold (say 5000) on the number of followers that will be collected. Note that the typical Twitter user has about 200 followers (many of which are bots or spam accounts).
In practice, the Follow network may not be as userful as the “SEARCH” network based on an active “Mention” or “Reply” from one user to another. A “Follow” may not indicate any awareness or exposure to the other user’s content. In contrast, Reply and Mention are stronger indicators of content exposure and engagement.
Hello!
Thanks for the interest in NodeXL!
Twitter’s API data volumes can vary based on factors internal to Twitter.
NodeXL will execute the same calls every time, but Twitter’s results may vary.
We do find that in some cases a delay of 24 hours will return the volumes delivered by Twitter to higher volumes.
Only a commercial feed from Twitter can guarantee a sustained rate of data. These services are currently very expensive.
If you would like to share the query you are running, I can try to replicate it here – perhaps I will get more data?
Regards,
Marc
