Complete NodeXL Release History
- If you use third-party graph data importers, such as the Social Network Importer for NodeXL, you can no longer put the importer files into a built-in PlugIns folder, because that folder no longer exists. (On English computers, the built-in PlugIns folder was either "C:\Program Files (x86)\Social Media Research Foundation\NodeXL Excel Template\PlugIns" or "C:\Program Files\Social Media Research Foundation\NodeXL Excel Template\PlugIns".) Instead, you should put the importer files into any folder of your choice, and then tell NodeXL where that folder is via the NodeXL, Data, Import, Import Options item on the Excel ribbon.
- Bug fix: In some versions of Excel, the popup menu that appears when you right-click a cell in the Edges, Vertices and Groups worksheets did not include custom NodeXL menu items.
- Bug fix, for programmers only: If the NodeXL class libraries were used in an application that targeted .NET 4.0, the shaded rectangles behind vertex label annotations were drawn in the wrong place.
- Bug fix, for programmers only: You could not build the Release version of the NodeXL solution without first building the Debug version.
- It now takes significantly less time to import a graph from the NodeXL Graph Server. (This is a server-side change, so you don't need version 188.8.131.52 to notice the difference.)
- Graphs imported from the NodeXL Graph Server now include vertices for people who were replied to or mentioned by the people who tweeted the specified term but who didn't tweet the term themselves. (Note 1: Collection of the additional vertices started on 2013-08-21. Networks that span earlier dates might include some additional vertices if they happen to already be in the collection database. Note 2: This is a server-side change, so you don't need version 184.108.40.206 to notice the difference.)
- Checking "Expand URLs in tweets" in the Import from NodeXL Graph Server dialog box no longer slows the import to a crawl. It can still take a long time to get the network if it has thousands of edges and vertices, but expanding URLs is now much faster. (This is a server-side change, so you don't actually need version 220.127.116.11 to notice the difference.)
- Bug fix: When it looked for user names in tweets, NodeXL was treating underscores as discardable punctuation. This resulted in @john_doe being interpreted as @john.
- Bug fix: If your workbook had a file name that contained certain non-English characters (Korean characters, for example) and you attempted to export the workbook via NodeXL, Data, Export, To Email, you would get a message saying "A problem occurred while sending the email."
- If you import a network from the NodeXL Graph Server, the graph summary (NodeXL, Graph, Summary) now includes more information, including the date range of the tweets in the network.
- The Data Import section of the Graph Summary for all Twitter, YouTube and Flickr network is now broken into paragraphs for clarity.
- When it looks for user names in tweets, NodeXL now ignores most punctuation. For example, the user name "john" in the tweet "Hello,@john" wasn't being detected, because it was preceded by a comma instead of a space.
- NodeXL will now pause for an extra 15 seconds when Twitter rate limits are reached. This is an attempt to work around a problem where Twitter occasionally refuses to provide more information even after NodeXL pauses for the time specified by Twitter. The symptom of that problem is a message that includes the text "A likely cause is that you have made too many Twitter requests in the last 15 minutes." (This might not fix the problem, the cause of which is unknown.)
- If you import a Twitter search network and tell NodeXL to calculate Twitter search network top items (NodeXL, Analysis, Graph Metrics), then the following columns now get added to the Vertices worksheet: Top URLs in Tweet by Count, Top URLs in Tweet by Salience, Top Domains in Tweet by Count, Top Domains in Tweet by Salience, Top Hashtags in Tweet by Count, Top Hashtags in Tweet by Salience, Top Words in Tweet by Count, Top Words in Tweet by Salience, Top Word Pairs in Tweet by Count, Top Word Pairs in Tweet by Salience.
- When importing a Twitter network, if Twitter unexpectedly closes the network connection, then NodeXL will now try to reestablish the connection. (The symptom of this problem is a message that includes the text "[IOException]: Unable to read data from the transport connection: The connection was closed.")
- An importer for a new Graph Server has been added. The Graph Server is currently private.
- Bug fix: If you used NodeXL, Analysis, Subgraph Images and one of your vertices had a name that was "reserved" by Windows (con, lpt, nul, and several others), you would get an error message that included the text "[ExternalException]: A generic error occurred in GDI+". Note that subgraph image file names now always start with "Img-", as in "Img-con.png".
- This release wraps up a set of enhancements and bug fixes that were previously included in a series of experimental private releases. All changes since the last public release (18.104.22.168) have to do with importing Twitter networks.
- An experiment involving "shared term" edges in the Twitter search network is still in progress, and those edges are not included in this release. (They were not included in version 22.214.171.124, either.)
- This release is functionally identical to version 126.96.36.199.
(2013-06-17, private release)
- In the Twitter search network, vertices are now added to the graph for people who were replied to or mentioned by the people who actually tweeted the specified term.
- Bug fix: In the Twitter networks, if you checked "Expand URLs in tweets" and a malformed URL was provided by Twitter, you would get a "Partial Network" message and then the graph would have no edges. The Partial Network details included the text "[UriFormatException]: Invalid URI: The format of the URI could not be determined". Now, NodeXL doesn't attempt to expand the bad URL.
- Bug fix: When getting a Twitter search network, you would sometimes get a "Partial Network" message with details that included the text "[KeyNotFoundException]: The given key was not present in the dictionary." (This was caused by Twitter giving NodeXL a tweet that included no information about the tweeter. NodeXL now ignores such tweets.)
(2013-05-19, private release)
- The Twitter Search Network now uses experimental shared term thresholds. This is part of an effort to obtain meaningful edges without running into Twitter's new rate limits.
(2013-05-01, private release)
- The shared word user threshold can now be specified in the network configuration file used by the Network Server program. (For advanced users of private releases only.)
- Bug fix: If you specified shared hashtag, URL, word, or word pair edge relationships in the Import from Twitter Search Network dialog box, the graph summary (NodeXL, Graph, Summary) did not mention the fact that the graph included those edges. (Private releases only.)
(2013-04-25, private release)
- Bug fix: If you imported a Twitter network that included the empty hyperlink "http://" somewhere in the network's text, Excel would refuse to save the workbook. The error message started with "Errors were detected while saving..." This is an Excel bug that will also arise if you type "http://" directly into a cell. This change does not fix the latter problem.
(2013-04-24, private release)
- If you check "add statistic columns to the Vertices worksheet" in the Import from Twitter Search Network dialog box, no additional time will be required to get the network. This used to require additional Twitter requests, and it was marked as "slower" in the dialog box.
(2013-04-08, private release)
- Same as 188.8.131.52, but with additional edge options.
- Bug fix: In versions 184.108.40.206 and 237, if you entered a space (or a colon, or a few other special characters) into the "Add a vertex for each..." textbox on the Import from Twitter Search Network dialog box, you would get a message that included the text, "The Twitter Web service refused to provide the requested information."
(2013-03-25, private release)
- Same as 220.127.116.11, but with additional edge options.
Go to Page 2 >>
- There are some major changes in NodeXL's Twitter importers. See Changes in NodeXL's Twitter Importers for more information.
- When you use dynamic filters (NodeXL, Analysis, Dynamic Filters), filtering an edge will automatically filter its adjacent vertices if the filtering causes those vertices to become isolates.
- If you set the Visibility of vertex X to "Skip" and vertex X has adjacent vertices that are connected only to vertex X, then those adjacent vertices are now skipped as well. Previously, the adjacent vertices would remain in the graph as isolates.
- For programmers: The NodeXL source code is now available on the CodePlex "Source Code" tab. The source code will no longer be provided as separate releases on the Downloads tab.