task
stringlengths 12
101
| input
stringlengths 0
7.31k
| output
stringlengths 1
14.7k
| options
sequence | pageTitle
stringlengths 0
351
| outputColName
stringlengths 1
2.64k
| url
stringlengths 18
289
| wdcFile
stringlengths 68
75
|
|---|---|---|---|---|---|---|---|
4c2fc7dc_esBranchIntegration___Pig_Wiki__Comments | [JIRA] PIG-231 [Done] Yes [Comments] | validation of files in ship/cache specs | [] | PigTypesBranchIntegration - Pig Wiki | Comments | http://wiki.apache.org/pig/PigTypesBranchIntegration?highlight=QueryParser | 9/1438042990611.52_20150728002310-00310-ip-10-236-191-2_262322390_2.json |
4c2fc7dc_esBranchIntegration___Pig_Wiki__Comments | [JIRA] PIG-229 [Done] Yes [Comments] | streaming does not handle errors on load function | [] | PigTypesBranchIntegration - Pig Wiki | Comments | http://wiki.apache.org/pig/PigTypesBranchIntegration?highlight=QueryParser | 9/1438042990611.52_20150728002310-00310-ip-10-236-191-2_262322390_2.json |
4c2fc7dc_esBranchIntegration___Pig_Wiki__Comments | [JIRA] PIG-227 [Done] Yes [Comments] | parsing problems for streaming define | [] | PigTypesBranchIntegration - Pig Wiki | Comments | http://wiki.apache.org/pig/PigTypesBranchIntegration?highlight=QueryParser | 9/1438042990611.52_20150728002310-00310-ip-10-236-191-2_262322390_2.json |
4c2fc7dc_esBranchIntegration___Pig_Wiki__Comments | [JIRA] PIG-224 [Done] Yes [Comments] | streaming returns always returns 127 | [] | PigTypesBranchIntegration - Pig Wiki | Comments | http://wiki.apache.org/pig/PigTypesBranchIntegration?highlight=QueryParser | 9/1438042990611.52_20150728002310-00310-ip-10-236-191-2_262322390_2.json |
4c2fc7dc_esBranchIntegration___Pig_Wiki__Comments | [JIRA] PIG-228 [Done] Yes [Comments] | names for secondary streaming outputs don't match the spec | [] | PigTypesBranchIntegration - Pig Wiki | Comments | http://wiki.apache.org/pig/PigTypesBranchIntegration?highlight=QueryParser | 9/1438042990611.52_20150728002310-00310-ip-10-236-191-2_262322390_2.json |
4c2fc7dc_esBranchIntegration___Pig_Wiki__Comments | [JIRA] PIG-216 [Done] Yes [Comments] | streaming does not handle commands with pipes | [] | PigTypesBranchIntegration - Pig Wiki | Comments | http://wiki.apache.org/pig/PigTypesBranchIntegration?highlight=QueryParser | 9/1438042990611.52_20150728002310-00310-ip-10-236-191-2_262322390_2.json |
4c2fc7dc_esBranchIntegration___Pig_Wiki__Comments | [JIRA] PIG-188 [Done] Yes [Comments] | streaming error | [] | PigTypesBranchIntegration - Pig Wiki | Comments | http://wiki.apache.org/pig/PigTypesBranchIntegration?highlight=QueryParser | 9/1438042990611.52_20150728002310-00310-ip-10-236-191-2_262322390_2.json |
4c2fc7dc_esBranchIntegration___Pig_Wiki__Comments | [JIRA] PIG-184 [Done] Yes [Comments] | Parsing issue on the stream statement? | [] | PigTypesBranchIntegration - Pig Wiki | Comments | http://wiki.apache.org/pig/PigTypesBranchIntegration?highlight=QueryParser | 9/1438042990611.52_20150728002310-00310-ip-10-236-191-2_262322390_2.json |
4c2fc7dc_esBranchIntegration___Pig_Wiki__Comments | [JIRA] PIG-181 [Done] Yes [Comments] | Bug in streaming | [] | PigTypesBranchIntegration - Pig Wiki | Comments | http://wiki.apache.org/pig/PigTypesBranchIntegration?highlight=QueryParser | 9/1438042990611.52_20150728002310-00310-ip-10-236-191-2_262322390_2.json |
4c2fc7dc_esBranchIntegration___Pig_Wiki__Comments | [JIRA] PIG-174 [Done] Yes [Comments] | Bug in streaming | [] | PigTypesBranchIntegration - Pig Wiki | Comments | http://wiki.apache.org/pig/PigTypesBranchIntegration?highlight=QueryParser | 9/1438042990611.52_20150728002310-00310-ip-10-236-191-2_262322390_2.json |
4c2fc7dc_esBranchIntegration___Pig_Wiki__Comments | [JIRA] PIG-154 [Done] Yes [Comments] | Move DEFINE and STORE parsing into QueryParser from GruntParser | [] | PigTypesBranchIntegration - Pig Wiki | Comments | http://wiki.apache.org/pig/PigTypesBranchIntegration?highlight=QueryParser | 9/1438042990611.52_20150728002310-00310-ip-10-236-191-2_262322390_2.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Comments [Required?] Yes [Notes] | Interaction is important. I want feedback on my genealogy blog. I want to know if I’m right or wrong with the information. I want a debate of the information to get to the truth. Most importantly, I want to hear from friends and relatives who may know the truth, whom I haven’t met yet. The greatest resource a family history researcher can find is another family member also researching the family tree. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Static Family Tree Information, and/or Informational And Educational Content [Required?] Yes [Notes] | You can post only information about your family’s history, or combine it with educational and informational article on how you research, adventures in research, and various genealogy information and resources. After discussion with family members, we agreed that a combination of family, news, and education would give our blog more value to everyone and hopefully spark enthusiasm in others. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Feeds [Required?] Yes [Notes] | Feeds are now necessary for monitoring activity on a blog. Feeds are required to help fellow family researchers monitor our discoveries and articles. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Podcasts [Required?] Yes [Notes] | We have many recorded interviews with now-deceased ancestors, as well as recordings of stories of childhood memories, interviews with each other, and more. Many of these will be turned into podcasts. I don’t know the file sizes of what the family has, so I’ll guess that I need at least 250 MB storage space for these, though I might be underestimating this. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Video [Required?] Yes [Notes] | Like audio recordings, we have video of our family history we’d like to share. I’m just not sure how much storage space will be needed for both audio and video, now and in the future. The general rule of thumb for moderate resolution video files is one megabyte per one minute of video. Our current estimate is 500 megabytes, which might be high but gives us room to grow. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Tables [Required?] Yes [Notes] | Tables are for displaying data, and we will have some data specific information. Building tables in many blogging programs means hand coding, so familiarity with HTML table tag codes is usually required. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Graphics [Required?] Yes [Notes] | We will not use a lot of gimmicky genealogy graphic images like many genealogy sites do. I like my blogs to be clean, allowing the photographs and writing to be the focal points. I also hate distractions on web pages. So I estimate at most 100K in storage space for clip art graphics, if other members of our team want them. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Photographic Images [Required?] Yes [Notes] | We will be hosting a lot of photographs. Typically, I keep photographic images at 50K or below, but with a genealogy blog, some photograph file sizes will be larger for maximum viewing resolution. I estimate photography file storage space on the server to be 500 megabytes with plenty of room to grow. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Thumbnail And Full Size Image Links [Required?] Yes [Notes] | A thumbnail and full size image link is a technique of having two copies of an image linked together. The first smaller size is shown on the blog post, wrapped in a link that, when clicked, takes the visitor to a larger perspective of the image, usually a higher resolution for viewing of photographic details. A thumbnail image ranges from 3K to 30K depending upon the size, and the full size image could easily be 100K – 300K. If we have one hundred 300K full size photographic images with their accompanying thumbnails, that’s 30 megabytes. So I should probably add another 500 megabytes of file storage to increase photo storage space to 1 gig just to make sure I have plenty of room. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Scanned Documents [Required?] Yes [Notes] | There will be a lot of scanned documents on the blog. These will most likely be used as thumbnail-to-larger-image links, creating two copies of each image, small and large. Scanned documents at the large, viewable and readable size, will probably be fairly large, possibly 150K – 350K, though I doubt few will be larger. I think the 1-2 gig range for all photography and scanned document images is a good estimate for file storage space. Don’t forget about the techniques and technology of scanning such documents and photographs for displaying within the blog. A good quality scanner, scanning software, photo editing software, and possibly Optical Character Recognition (OCR) software may be required to support such documentation on the blog. The programs which come with most scanners are inadequate to do this well, so anticipate buying additional software. This equipment and software should figure into your blog’s budget as part of the cost of the blog. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Blogroll/Link Lists [Required?] Yes [Notes] | A genealogy blog is connects family and other genealogy researchers together. We will have a lot of resource link lists to incorporate. If the blog platform offers easy blogrolls and link lists, all the better. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Forums [Required?] Maybe [Notes] | Some big family genealogy sites feature forums where family members can discuss their research and findings. At this point, I will not be incorporating a forum into our family history blog, though I might discuss it in this series. I want the ability to add this in the future, so I will need to choose a blogging platform that will easily integrate with a forum, and a host with optional forum services and capabilities. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Wiki [Required?] Doubtful [Notes] | A wiki is a contribution document, much like the Wikipedia, free online encyclopedia. Some family history blogs use these as a platform for building information up about family members, creating a family encyclopedia. We probably won’t need one, but I want to keep my options open, so again, I need a blogging platform that will allow incorporation of a wiki and a host with wiki capabilities. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Live Chats [Required?] No [Notes] | If I were retired and doing this full time, I might want to make live chats for our family history blog available. My current lifestyle doesn’t work with live chats. Yours might. If it does, make sure this option is available through your web host. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Email Subscriptions [Required?] Yes [Notes] | Like feeds, email subscription notifications to the blog are another way of monitoring a blog. I want to go farther with these and have category-specific email subscriptions, as someone researching the Knapp family would probably not want information on the Anderson family. I need to do research on how to make this work. I need to ensure email services are available from the web host. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Newsletter Registration [Required?] Maybe [Notes] | Some genealogy blogs feature frequent newsletters sent by email to catch people up on the latest family or research news. I think feeds and email subscription notifications are replacing emailed newsletters, but I want this option open in case someone in the family would like to take on this project. The process of newsletter subscription, mailing list maintenance, and emailing is often a feature included in some hosting services. There are other off-site services available, free and paid, worth investigating when the time comes. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Replace The Built-In Search Function [Required?] Yes [Notes] | Most blogs’ search capabilities are limited to post content and not static pages. Because our family history blog will include static pages and non-integrated web pages, tools, and utilities, a Google or Yahoo site search will be added to maximize site search capabilities. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Site Registration [Required?] No [Notes] | Many genealogy blogs have a small public access area and then a user registration area for access to private or restricted information. Some simply require approved registration, others require a fee. As things stand now, I do not want to restrict access to any family history information. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Static Pages [Required?] Yes [Notes] | A static page has two meanings when it comes to WordPress. A static page is any page that may look like your blog web page design pages, but isn’t incorporated into the PHP coding structure. It just has the look but is actually a separate, stand alone web page. In WordPress, a Page is a pseudo-static page. It stands alone as it is not part of the chronological flow of the blog, but it is not a physically separate web page. It is generated by the program. I will need both. Any blog needs Pages like “About”, “Contact”, and so on. A genealogy blog takes advantage of genealogy software to produce web pages of content, data, and information. While some of these can be cleaned up and inserted into a WordPress Page, some cannot and will have to become static and separate pages. Because I want a uniform look for the entire site, I will need to understand how WordPress Themes and web design works to clean these up for inclusion and integration. Static web pages also take up space on the hosting server as they are static HTML/XHTML pages. I’m not sure how many the genealogy blog will require, maybe 5-20. Look for an average of 10 static web pages at an estimated 60K each (with images) is 600K to add to the total file storage requirements. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Strong Inter-Linking And Relationships With Outside Resources And Content [Required?] Yes [Notes] | There is a lot of information on the web about my ancestors. I don’t want to be redundant, so when we can, we will link to these. There are also many services which allow free and paid sharing of family history information and family trees, and we may take advantage of these and create links to them. I want our direct family information to stay on our site as much as possible without repeating the work of others, so creating strong link relationships between our content and off-site content will be tricky. A policy needs to be established for the blog on what goes where and how to link to content off-site. My biggest concern is showcasing family tree information off-site and encouraging a visitor to leave the site and not find their way back. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Integration Of Non-Blog Format Web Pages [Required?] Yes [Notes] | As discussed under Pages, there will be non-blog format web pages that need integration within the blog to maintain a consistent look and feel. This technique requires some familiarity with web page design and blog codes, though eventually a template can be made up so that it is just a copy and paste and upload task. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Integration Of Non-Wordpress Tools And Utilities [Required?] Yes [Notes] | There are several genealogy tools and utilities that may help display information about our family and family tree that work outside of the blog but on-site. Finding a method of incorporating these into the look and feel of the site will take some technical expertise, though they are becoming much easier to use. The issue of such incorporation as related to researching a blog hosting service and costs is to understand what the programs requirements in order to work on your blog’s site. They will take up server storage space. Estimate 50K to 10 MEGs of storage space to install and then an additional 1-20 megabytes of storage space to accommodate your family information. At a minimum, these programs may require MySQL database, PHP, Apache, FTP access, CGI, and/or Pearl. Research these first to make sure the web host you choose has the options these tools require before investing in a host. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Name Lists [Required?] Yes [Notes] | Name lists are the list of names within the family tree. These will be hosted on a static or pseudo-static Page. They can be generated by genealogy software or manually. Right now, I anticipate the name lists to be created somewhat manually as the links in the names should be to on-site searches, which are unique to each blog’s search link codes. If there is an easier way to encode name lists in links for displaying on a web page, I’d love to find it. More research needed. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Privacy and Permission Statements [Required?] Yes [Notes] | Do we need a lawyer? Maybe. Privacy and permission issues need to be clearly and publicly addressed on your blog. These are legal issues and are required by some countries and communities. There are many templates available to follow, but if you are serious about your genealogy blog’s rules and regulations pertaining to privacy, permissions, hold harmless, and other protections from publishing harm, you might want to run these by your lawyer, or one expert in these issues. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Multiple Users And Contributors [Required?] Yes [Notes] | I have several family members who want to help with this project. At issue is at what level they are willing to help and contribute. Some may email me their stories and research and I will post them on the blog. Others will want to post their own. Others might be techno-savvy enough to help dig into the code and process to help make things work. An easy-to-access and use blogging platform is critical. I need to learn about how the permissions and authorities levels work within my blogging platform, and ensure that the web hosting service I choose has email services such as email accounts and email forwarding for use by these contributors. I will also need to write up rules and regulations about such participation. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Multiple Administrators And Editors [Required?] Yes [Notes] | Like having multiple users and contributors, we may have multiple administrators and editors. Different from contributors, these are the decision makers. I need to understand how permission and authority levels work on the web host and blogging platform, and write up agreements and guidelines so we understand who makes what decisions, who can overturn them, how decisions are made, as well as clearly decide upon the “voice and style” of the blog to maintain a form of consistency. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Commerce/Shops [Required?] Maybe [Notes] | Several family members have written books about our family history. We might want to offer these for sale if there is an interest. Having the option to include a shopping cart with a web host is nice to have, just in case. We might also want to sell copies of family photographs and other items to cover reproduction and mailing costs, so this is something to think about when choosing a host. Adding an online shopping cart also increases file sizes, so make sure to add at least 50 MB or more to the storage space. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Auto-Responders [Required?] Maybe [Notes] | Auto-Responders work two ways. One is to respond to an email with an automated reply, much as you might use on your email when going out of town for a week or two. The others is to create an email link that would respond with information. For instance, if I had a research article series to help you research your family, after publishing it on my blog, I could package up the whole thing in text form and store it in the auto-responder. I’d make a link to the email address to that auto-responder saying, “If you would like to read this article series in its entirely, you can request it by email”. Click, enter your return email, hit send, and the article is emailed back to the requester. There are a variety of ways to use auto-responders, so consider this feature when choosing a web host. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Sub-Domains [Required?] Maybe [Notes] | Sub-domains are like websites within websites. This blog is actually a sub-domain of WordPress.com as lorelle.wordpress.com. You could have sub-domains for different family members such as smith.myfamilyhistoryblog.com or anderson.myfamilyhistoryblog.com. If you are running a huge genealogy site, then this is an option. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Web Traffic and Bandwidth [Required?] Yes [Notes] | Part of choosing a web host is determining how much traffic and bandwidth your genealogy blog will require. The two are interconnected. Each visitor automatically downloads the viewed web page content and design elements, which uses bandwidth. Each file downloaded adds to your bandwidth. A website with a lot of graphics and photographs will use up more bandwidth than one without. The number of visitors to your blog is your web traffic, and the more visitors visiting, and the more photographs they are viewing, the larger the bandwidth requirement. Add to this number files you might want to be specifically downloaded, such as GEDCOM files, then more bandwidth is necessary. In the simplest of terms. Honestly, I don’t expect many visitors. After all, how many people are really interested in the Elwell family? Knapp family? Andersons or Wests? Not thousands every month. So I expect that actual traffic levels to be between 50-500 visitors a month. At the maximum, if an average page on the genealogy blog totals to 300K in bandwidth (with a bunch of photographs) for 500 visitors, that would be 15 megabytes of bandwidth per month. Most web hosts offer 250 megabytes to 2 gigs as their smallest package, so that would be plenty. Remember, if your web traffic level is exceeded, you will be charged. So allow for plenty of leeway. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Citations [Required?] Yes [Notes] | Citations will be used. The issue is how. A uniform method needs to be developed on how to cite, what the citation looks like, and how to link to cites, and whether the citations link to footnotes or separate source pages. Web page design expertise will be needed. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Footnotes [Required?] Yes [Notes] | Footnotes will be used throughout the site. I need to find a way of making the process of footnoting as simple and easy as possible for the non-technical users. The look of the footnotes also has to be incorporated into the web page design. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Credits [Required?] Yes [Notes] | Credits also need to be formatted and a consistent style developed. Policies on how, when, and where to credit also need to be developed and published as part of the blog’s guidelines. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
2f80e9e9_My_Blog___Lorelle_on_WordPress__Notes | [Feature] Captions [Required?] Yes [Notes] | Captions will be used frequently with photographs and scanned documents. They need a uniform look and they need to be very easy to use. The information in the captions may include citations, credits, and footnote links, so a variety of coding elements will have to be taken into consideration in developing and styling captions. | [] | Genealogy Blog: Determining What Features I Want in My Blog « Lorelle on WordPress | Notes | https://lorelle.wordpress.com/2006/08/03/genealogy-blog-determining-what-features-i-want-in-my-blog/?like=1&source=post_flair&_wpnonce=ed3d838804 | 32/1438042990603.54_20150728002310-00302-ip-10-236-191-2_863370096_0.json |
866876f0_Loss__Obesity_Clinic_Inch_Loss__LIPOSUCTION | [0] Fat Cells [DIET / EXERCISE] Non targeted [OTHER SLIMMING CLINICS] Non Targeted [INSTASCULPT] Targeted [LIPOSUCTION] | Targeted | [
[
"T",
"a",
"r",
"g",
"e",
"t",
"e",
"d"
],
[
"Q",
"u",
"i",
"c",
"k"
],
[
"S",
"u",
"r",
"g",
"e",
"r",
"y"
],
[
"R",
"i",
"s",
"k",
" ",
"o",
"f",
" ",
"s",
"u",
"r",
"g",
"e",
"r",
"y"
],
[
"H",
"o",
"s",
"p",
"i",
"t",
"a",
"l",
"i",
"z",
"a",
"t",
"i",
"o",
"n"
],
[
"S",
"o",
"m",
"e",
" ",
"p",
"a",
"i",
"n"
]
] | Treatments - Body Sculpting, Toning | Lipolysis Treatment | Non Surgical Weight Loss, Obesity Clinic,Inch Loss | LIPOSUCTION | http://www.insta-sculpt.com/body_sculpting_treatment.html | 7/1438042988311.72_20150728002308-00176-ip-10-236-191-2_518604717_1.json |
866876f0_Loss__Obesity_Clinic_Inch_Loss__LIPOSUCTION | [0] Effect [DIET / EXERCISE] Gradual [OTHER SLIMMING CLINICS] Gradual [INSTASCULPT] Gradual [LIPOSUCTION] | Quick | [
[
"T",
"a",
"r",
"g",
"e",
"t",
"e",
"d"
],
[
"Q",
"u",
"i",
"c",
"k"
],
[
"S",
"u",
"r",
"g",
"e",
"r",
"y"
],
[
"R",
"i",
"s",
"k",
" ",
"o",
"f",
" ",
"s",
"u",
"r",
"g",
"e",
"r",
"y"
],
[
"H",
"o",
"s",
"p",
"i",
"t",
"a",
"l",
"i",
"z",
"a",
"t",
"i",
"o",
"n"
],
[
"S",
"o",
"m",
"e",
" ",
"p",
"a",
"i",
"n"
]
] | Treatments - Body Sculpting, Toning | Lipolysis Treatment | Non Surgical Weight Loss, Obesity Clinic,Inch Loss | LIPOSUCTION | http://www.insta-sculpt.com/body_sculpting_treatment.html | 7/1438042988311.72_20150728002308-00176-ip-10-236-191-2_518604717_1.json |
866876f0_Loss__Obesity_Clinic_Inch_Loss__LIPOSUCTION | [0] Technique [DIET / EXERCISE] Non specific [OTHER SLIMMING CLINICS] Non Scientific as Viibration,heat pads or water disposition [INSTASCULPT] Therapeutic massage [LIPOSUCTION] | Surgery | [
[
"T",
"a",
"r",
"g",
"e",
"t",
"e",
"d"
],
[
"Q",
"u",
"i",
"c",
"k"
],
[
"S",
"u",
"r",
"g",
"e",
"r",
"y"
],
[
"R",
"i",
"s",
"k",
" ",
"o",
"f",
" ",
"s",
"u",
"r",
"g",
"e",
"r",
"y"
],
[
"H",
"o",
"s",
"p",
"i",
"t",
"a",
"l",
"i",
"z",
"a",
"t",
"i",
"o",
"n"
],
[
"S",
"o",
"m",
"e",
" ",
"p",
"a",
"i",
"n"
]
] | Treatments - Body Sculpting, Toning | Lipolysis Treatment | Non Surgical Weight Loss, Obesity Clinic,Inch Loss | LIPOSUCTION | http://www.insta-sculpt.com/body_sculpting_treatment.html | 7/1438042988311.72_20150728002308-00176-ip-10-236-191-2_518604717_1.json |
866876f0_Loss__Obesity_Clinic_Inch_Loss__LIPOSUCTION | [0] Risk [DIET / EXERCISE] No risk [OTHER SLIMMING CLINICS] Redness, Burns or Dehydration [INSTASCULPT] No risk [LIPOSUCTION] | Risk of surgery | [
[
"T",
"a",
"r",
"g",
"e",
"t",
"e",
"d"
],
[
"Q",
"u",
"i",
"c",
"k"
],
[
"S",
"u",
"r",
"g",
"e",
"r",
"y"
],
[
"R",
"i",
"s",
"k",
" ",
"o",
"f",
" ",
"s",
"u",
"r",
"g",
"e",
"r",
"y"
],
[
"H",
"o",
"s",
"p",
"i",
"t",
"a",
"l",
"i",
"z",
"a",
"t",
"i",
"o",
"n"
],
[
"S",
"o",
"m",
"e",
" ",
"p",
"a",
"i",
"n"
]
] | Treatments - Body Sculpting, Toning | Lipolysis Treatment | Non Surgical Weight Loss, Obesity Clinic,Inch Loss | LIPOSUCTION | http://www.insta-sculpt.com/body_sculpting_treatment.html | 7/1438042988311.72_20150728002308-00176-ip-10-236-191-2_518604717_1.json |
866876f0_Loss__Obesity_Clinic_Inch_Loss__LIPOSUCTION | [0] Hospitalization [DIET / EXERCISE] No hospitalization [OTHER SLIMMING CLINICS] No hospitalization [INSTASCULPT] No hospitalization [LIPOSUCTION] | Hospitalization | [
[
"T",
"a",
"r",
"g",
"e",
"t",
"e",
"d"
],
[
"Q",
"u",
"i",
"c",
"k"
],
[
"S",
"u",
"r",
"g",
"e",
"r",
"y"
],
[
"R",
"i",
"s",
"k",
" ",
"o",
"f",
" ",
"s",
"u",
"r",
"g",
"e",
"r",
"y"
],
[
"H",
"o",
"s",
"p",
"i",
"t",
"a",
"l",
"i",
"z",
"a",
"t",
"i",
"o",
"n"
],
[
"S",
"o",
"m",
"e",
" ",
"p",
"a",
"i",
"n"
]
] | Treatments - Body Sculpting, Toning | Lipolysis Treatment | Non Surgical Weight Loss, Obesity Clinic,Inch Loss | LIPOSUCTION | http://www.insta-sculpt.com/body_sculpting_treatment.html | 7/1438042988311.72_20150728002308-00176-ip-10-236-191-2_518604717_1.json |
866876f0_Loss__Obesity_Clinic_Inch_Loss__LIPOSUCTION | [0] Pain [DIET / EXERCISE] Painless [OTHER SLIMMING CLINICS] Occassionally Painful [INSTASCULPT] Painless [LIPOSUCTION] | Some pain | [
[
"T",
"a",
"r",
"g",
"e",
"t",
"e",
"d"
],
[
"Q",
"u",
"i",
"c",
"k"
],
[
"S",
"u",
"r",
"g",
"e",
"r",
"y"
],
[
"R",
"i",
"s",
"k",
" ",
"o",
"f",
" ",
"s",
"u",
"r",
"g",
"e",
"r",
"y"
],
[
"H",
"o",
"s",
"p",
"i",
"t",
"a",
"l",
"i",
"z",
"a",
"t",
"i",
"o",
"n"
],
[
"S",
"o",
"m",
"e",
" ",
"p",
"a",
"i",
"n"
]
] | Treatments - Body Sculpting, Toning | Lipolysis Treatment | Non Surgical Weight Loss, Obesity Clinic,Inch Loss | LIPOSUCTION | http://www.insta-sculpt.com/body_sculpting_treatment.html | 7/1438042988311.72_20150728002308-00176-ip-10-236-191-2_518604717_1.json |
c5ab7f65__2_7_1___NodeManager_REST_APIs__Data_Type | [Properties] id [Description] The NodeManager id [Data Type] | long | [
[
"l",
"o",
"n",
"g"
],
[
"s",
"t",
"r",
"i",
"n",
"g"
],
[
"b",
"o",
"o",
"l",
"e",
"a",
"n"
]
] | Apache Hadoop 2.7.1 – NodeManager REST APIs | Data Type | http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html | 9/1438042988511.77_20150728002308-00242-ip-10-236-191-2_115138502_0.json |
c5ab7f65__2_7_1___NodeManager_REST_APIs__Data_Type | [Properties] nodeHostName [Description] The host name of the NodeManager [Data Type] | string | [
[
"l",
"o",
"n",
"g"
],
[
"s",
"t",
"r",
"i",
"n",
"g"
],
[
"b",
"o",
"o",
"l",
"e",
"a",
"n"
]
] | Apache Hadoop 2.7.1 – NodeManager REST APIs | Data Type | http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html | 9/1438042988511.77_20150728002308-00242-ip-10-236-191-2_115138502_0.json |
c5ab7f65__2_7_1___NodeManager_REST_APIs__Data_Type | [Properties] totalPmemAllocatedContainersMB [Description] The amount of physical memory allocated for use by containers in MB [Data Type] | long | [
[
"l",
"o",
"n",
"g"
],
[
"s",
"t",
"r",
"i",
"n",
"g"
],
[
"b",
"o",
"o",
"l",
"e",
"a",
"n"
]
] | Apache Hadoop 2.7.1 – NodeManager REST APIs | Data Type | http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html | 9/1438042988511.77_20150728002308-00242-ip-10-236-191-2_115138502_0.json |
c5ab7f65__2_7_1___NodeManager_REST_APIs__Data_Type | [Properties] totalVmemAllocatedContainersMB [Description] The amount of virtual memory allocated for use by containers in MB [Data Type] | long | [
[
"l",
"o",
"n",
"g"
],
[
"s",
"t",
"r",
"i",
"n",
"g"
],
[
"b",
"o",
"o",
"l",
"e",
"a",
"n"
]
] | Apache Hadoop 2.7.1 – NodeManager REST APIs | Data Type | http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html | 9/1438042988511.77_20150728002308-00242-ip-10-236-191-2_115138502_0.json |
c5ab7f65__2_7_1___NodeManager_REST_APIs__Data_Type | [Properties] totalVCoresAllocatedContainers [Description] The number of virtual cores allocated for use by containers [Data Type] | long | [
[
"l",
"o",
"n",
"g"
],
[
"s",
"t",
"r",
"i",
"n",
"g"
],
[
"b",
"o",
"o",
"l",
"e",
"a",
"n"
]
] | Apache Hadoop 2.7.1 – NodeManager REST APIs | Data Type | http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html | 9/1438042988511.77_20150728002308-00242-ip-10-236-191-2_115138502_0.json |
c5ab7f65__2_7_1___NodeManager_REST_APIs__Data_Type | [Properties] lastNodeUpdateTime [Description] The last timestamp at which the health report was received (in ms since epoch) [Data Type] | long | [
[
"l",
"o",
"n",
"g"
],
[
"s",
"t",
"r",
"i",
"n",
"g"
],
[
"b",
"o",
"o",
"l",
"e",
"a",
"n"
]
] | Apache Hadoop 2.7.1 – NodeManager REST APIs | Data Type | http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html | 9/1438042988511.77_20150728002308-00242-ip-10-236-191-2_115138502_0.json |
c5ab7f65__2_7_1___NodeManager_REST_APIs__Data_Type | [Properties] healthReport [Description] The diagnostic health report of the node [Data Type] | string | [
[
"l",
"o",
"n",
"g"
],
[
"s",
"t",
"r",
"i",
"n",
"g"
],
[
"b",
"o",
"o",
"l",
"e",
"a",
"n"
]
] | Apache Hadoop 2.7.1 – NodeManager REST APIs | Data Type | http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html | 9/1438042988511.77_20150728002308-00242-ip-10-236-191-2_115138502_0.json |
c5ab7f65__2_7_1___NodeManager_REST_APIs__Data_Type | [Properties] nodeHealthy [Description] true/false indicator of if the node is healthy [Data Type] | boolean | [
[
"l",
"o",
"n",
"g"
],
[
"s",
"t",
"r",
"i",
"n",
"g"
],
[
"b",
"o",
"o",
"l",
"e",
"a",
"n"
]
] | Apache Hadoop 2.7.1 – NodeManager REST APIs | Data Type | http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html | 9/1438042988511.77_20150728002308-00242-ip-10-236-191-2_115138502_0.json |
c5ab7f65__2_7_1___NodeManager_REST_APIs__Data_Type | [Properties] nodeManagerVersion [Description] Version of the NodeManager [Data Type] | string | [
[
"l",
"o",
"n",
"g"
],
[
"s",
"t",
"r",
"i",
"n",
"g"
],
[
"b",
"o",
"o",
"l",
"e",
"a",
"n"
]
] | Apache Hadoop 2.7.1 – NodeManager REST APIs | Data Type | http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html | 9/1438042988511.77_20150728002308-00242-ip-10-236-191-2_115138502_0.json |
c5ab7f65__2_7_1___NodeManager_REST_APIs__Data_Type | [Properties] nodeManagerBuildVersion [Description] NodeManager build string with build version, user, and checksum [Data Type] | string | [
[
"l",
"o",
"n",
"g"
],
[
"s",
"t",
"r",
"i",
"n",
"g"
],
[
"b",
"o",
"o",
"l",
"e",
"a",
"n"
]
] | Apache Hadoop 2.7.1 – NodeManager REST APIs | Data Type | http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html | 9/1438042988511.77_20150728002308-00242-ip-10-236-191-2_115138502_0.json |
c5ab7f65__2_7_1___NodeManager_REST_APIs__Data_Type | [Properties] nodeManagerVersionBuiltOn [Description] Timestamp when NodeManager was built(in ms since epoch) [Data Type] | string | [
[
"l",
"o",
"n",
"g"
],
[
"s",
"t",
"r",
"i",
"n",
"g"
],
[
"b",
"o",
"o",
"l",
"e",
"a",
"n"
]
] | Apache Hadoop 2.7.1 – NodeManager REST APIs | Data Type | http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html | 9/1438042988511.77_20150728002308-00242-ip-10-236-191-2_115138502_0.json |
c5ab7f65__2_7_1___NodeManager_REST_APIs__Data_Type | [Properties] hadoopVersion [Description] Version of hadoop common [Data Type] | string | [
[
"l",
"o",
"n",
"g"
],
[
"s",
"t",
"r",
"i",
"n",
"g"
],
[
"b",
"o",
"o",
"l",
"e",
"a",
"n"
]
] | Apache Hadoop 2.7.1 – NodeManager REST APIs | Data Type | http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html | 9/1438042988511.77_20150728002308-00242-ip-10-236-191-2_115138502_0.json |
c5ab7f65__2_7_1___NodeManager_REST_APIs__Data_Type | [Properties] hadoopBuildVersion [Description] Hadoop common build string with build version, user, and checksum [Data Type] | string | [
[
"l",
"o",
"n",
"g"
],
[
"s",
"t",
"r",
"i",
"n",
"g"
],
[
"b",
"o",
"o",
"l",
"e",
"a",
"n"
]
] | Apache Hadoop 2.7.1 – NodeManager REST APIs | Data Type | http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html | 9/1438042988511.77_20150728002308-00242-ip-10-236-191-2_115138502_0.json |
c5ab7f65__2_7_1___NodeManager_REST_APIs__Data_Type | [Properties] hadoopVersionBuiltOn [Description] Timestamp when hadoop common was built(in ms since epoch) [Data Type] | string | [
[
"l",
"o",
"n",
"g"
],
[
"s",
"t",
"r",
"i",
"n",
"g"
],
[
"b",
"o",
"o",
"l",
"e",
"a",
"n"
]
] | Apache Hadoop 2.7.1 – NodeManager REST APIs | Data Type | http://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html | 9/1438042988511.77_20150728002308-00242-ip-10-236-191-2_115138502_0.json |
30867fcc_AuditabilityReport_xml__Split_process | [0] Category [Op scan] SI [DRE] non-IV [VVPAT] SI [LVVPAT] non-IV [Witness] IV [E2E crypto] SI [Audit port] IV [Split process] | IV | [] | AuditabilityReport.xml | Split process | http://www.nist.gov/itl/vote/upload/AuditabilityReport_xml-7.htm | 16/1438042988312.76_20150728002308-00199-ip-10-236-191-2_633603196_0.json |
30867fcc_AuditabilityReport_xml__Split_process | [0] Error detection [Op scan] Direct verification, post-election audit [DRE] Indirect verification, integrity checks, event logs [VVPAT] Direct verification, post-election audit, integrity checks, event logs [LVVPAT] Direct verification by a selected sample, post-election audit, integrity checks, event logs [Witness] Post-election audit, event logs [E2E crypto] Count verification [Audit port] Depends on what connected [Split process] | Indirect verification, post-election audit, event logs | [] | AuditabilityReport.xml | Split process | http://www.nist.gov/itl/vote/upload/AuditabilityReport_xml-7.htm | 16/1438042988312.76_20150728002308-00199-ip-10-236-191-2_633603196_0.json |
30867fcc_AuditabilityReport_xml__Split_process | [0] Diagnosis [Op scan] Independent recount (possibly automated) [DRE] Contingent on defensive programming and design [VVPAT] VVPAT adds another record but also more points of failure [LVVPAT] Less than VVPAT [Witness] If witness device is sufficiently transparent and simple, should help diagnose faults in the other device [E2E crypto] No [Audit port] Depends on what connected [Split process] | Multiple devices and token make diagnosis more difficult | [] | AuditabilityReport.xml | Split process | http://www.nist.gov/itl/vote/upload/AuditabilityReport_xml-7.htm | 16/1438042988312.76_20150728002308-00199-ip-10-236-191-2_633603196_0.json |
30867fcc_AuditabilityReport_xml__Split_process | [0] Error correction [Op scan] Independent recount (possibly automated); no recovery if ballots are unreadable or destroyed [DRE] Duplicate electronic records allow recovery in case records are damaged but no recovery if votes were misrecorded [VVPAT] Reconstruct from VVPAT [LVVPAT] Less than VVPAT [Witness] Reconstruct from witness record [E2E crypto] Duplicate electronic records allow recovery in case records are damaged but no recovery if all copies fail cryptographic validation [Audit port] Depends on what connected [Split process] | Reconstruct from tokens | [] | AuditabilityReport.xml | Split process | http://www.nist.gov/itl/vote/upload/AuditabilityReport_xml-7.htm | 16/1438042988312.76_20150728002308-00199-ip-10-236-191-2_633603196_0.json |
30867fcc_AuditabilityReport_xml__Split_process | [0] Vote disambiguation [Op scan] Requires support for read verification [DRE] Yes [VVPAT] Yes [LVVPAT] Yes [Witness] Yes [E2E crypto] Yes [Audit port] Yes [Split process] | Yes | [] | AuditabilityReport.xml | Split process | http://www.nist.gov/itl/vote/upload/AuditabilityReport_xml-7.htm | 16/1438042988312.76_20150728002308-00199-ip-10-236-191-2_633603196_0.json |
30867fcc_AuditabilityReport_xml__Split_process | [0] Sampling audit [Op scan] Depends on ballot identification and reporting capabilities [DRE] Depends on ballot identification and reporting capabilities [VVPAT] Depends on ballot identification and reporting capabilities [LVVPAT] Yes, but sampling strategy should be auditor's prerogative, not determined in advance [Witness] Depends on ballot identification and reporting capabilities [E2E crypto] Yes (by voters) [Audit port] Depends on ballot identification and reporting capabilities [Split process] | Depends on ballot identification and reporting capabilities | [] | AuditabilityReport.xml | Split process | http://www.nist.gov/itl/vote/upload/AuditabilityReport_xml-7.htm | 16/1438042988312.76_20150728002308-00199-ip-10-236-191-2_633603196_0.json |
30867fcc_AuditabilityReport_xml__Split_process | [0] Multiple independent cast vote records [Op scan] No [DRE] No [VVPAT] Yes [LVVPAT] Only for sample [Witness] Contingent on the transparency of the witness device [E2E crypto] No [Audit port] Depends on what connected [Split process] | Contingent on independence of vote capture and verification stations, integrity of tokens | [] | AuditabilityReport.xml | Split process | http://www.nist.gov/itl/vote/upload/AuditabilityReport_xml-7.htm | 16/1438042988312.76_20150728002308-00199-ip-10-236-191-2_633603196_0.json |
30867fcc_AuditabilityReport_xml__Split_process | [0] Persistence of records [Op scan] Unique paper record subject to deterioration [DRE] Electronic records with back-ups; easier to preserve but also easier to lose [VVPAT] Both paper and electronic records; some insurance in having different types of records with different modes of failure [LVVPAT] Electronic records with back-ups; paper for sample only [Witness] Depends on type of witness device [E2E crypto] Depends on specific design [Audit port] Depends on what connected [Split process] | Token supposedly unalterable | [] | AuditabilityReport.xml | Split process | http://www.nist.gov/itl/vote/upload/AuditabilityReport_xml-7.htm | 16/1438042988312.76_20150728002308-00199-ip-10-236-191-2_633603196_0.json |
30867fcc_AuditabilityReport_xml__Split_process | [0] Security [Op scan] Protection of the sole record; ballot stuffing, chain voting, etc. [DRE] No direct verification; no independent record; requires secure and trustworthy software [VVPAT] VVPAT operational issues may cast false doubt on results [LVVPAT] Predetermined sampling limits power of audit [Witness] No direct verification; requires trustworthy witness devices, transparent witness records [E2E crypto] Requires correctly implemented cryptography [Audit port] Depends on what connected, protection of the audit port [Split process] | No direct verification; requires independence of vote capture and verification stations, high-integrity tokens; common vulnerabilities of vote capture and verification stations | [] | AuditabilityReport.xml | Split process | http://www.nist.gov/itl/vote/upload/AuditabilityReport_xml-7.htm | 16/1438042988312.76_20150728002308-00199-ip-10-236-191-2_633603196_0.json |
30867fcc_AuditabilityReport_xml__Split_process | [0] Accessibility [Op scan] Access features difficult to provide from paper ballot; must convert print to alternative forms and eliminate paper handling [DRE] Wide variety of access features can be readily provided from digital form of electronic ballot. No paper handling required. [VVPAT] Access features difficult to provide from VVPAT; must convert print to alternative forms when VVPAT is or can be ballot of record [LVVPAT] Not actually improved versus VVPAT but possibly more legally defensible since cast verification is not guaranteed to sighted voters1 [Witness] So long as the voter is not verifying the secondary archival record, no access features would be needed [E2E crypto] Depends on form of voter verification. Whatever media is used by the voter to verify (paper, web site, etc.) would need to be made accessible. [Audit port] Depends on what is connected and if the voter is verifying the output of the attached device. Paper output will be more difficult to make accessible than digital output. [Split process] | Depends on form of token. When token is paper, access features are difficult to deliver. When token is electronic, access features can more readily be provided but handling of token can still be access barrier. Both vote capture and verification stations must be accessible. | [] | AuditabilityReport.xml | Split process | http://www.nist.gov/itl/vote/upload/AuditabilityReport_xml-7.htm | 16/1438042988312.76_20150728002308-00199-ip-10-236-191-2_633603196_0.json |
30867fcc_AuditabilityReport_xml__Split_process | [0] Usability [Op scan] Ballots often marked incorrectly by voters [DRE] Potentially best available but depends on user interface design [VVPAT] Usability for audit tends to be poor [LVVPAT] Some voters get DRE experience, others get VVPAT experience [Witness] Same as DRE [E2E crypto] Process and added complexity not intuitive to the voter or poll worker [Audit port] Depends on what connected [Split process] | Two-stage process may be unintuitive | [] | AuditabilityReport.xml | Split process | http://www.nist.gov/itl/vote/upload/AuditabilityReport_xml-7.htm | 16/1438042988312.76_20150728002308-00199-ip-10-236-191-2_633603196_0.json |
30867fcc_AuditabilityReport_xml__Split_process | [0] Privacy [Op scan] Current accepted practice [DRE] Current accepted practice [VVPAT] Paper rolls record sequence of ballots [LVVPAT] An appropriate sampling strategy can improve privacy versus VVPAT [Witness] Potential to record sequence of ballots or (worst case) photograph the voter [E2E crypto] Possibly enhanced by obfuscation of choices [Audit port] Depends on what connected [Split process] | Combined issues of DRE + token (maybe paper) + verification | [] | AuditabilityReport.xml | Split process | http://www.nist.gov/itl/vote/upload/AuditabilityReport_xml-7.htm | 16/1438042988312.76_20150728002308-00199-ip-10-236-191-2_633603196_0.json |
30867fcc_AuditabilityReport_xml__Split_process | [0] System complexity (lower is better) [Op scan] 2 (accessible voting station + scanner) [DRE] 1 [VVPAT] 2 (DRE + printer) or 3 (+ readback from printout) [LVVPAT] 3 or 4 (... + overhead of having a variable process for the voting session) [Witness] 2 (vote capture + witness device) [E2E crypto] 2 (vote capture + cryptographic overhead) [Audit port] Depends on what connected [Split process] | 2 (vote capture + verification station) | [] | AuditabilityReport.xml | Split process | http://www.nist.gov/itl/vote/upload/AuditabilityReport_xml-7.htm | 16/1438042988312.76_20150728002308-00199-ip-10-236-191-2_633603196_0.json |
6ffaece7_Citizens_Bank_Privacy_Policy__Can_you_limit_this_sharing_ | For our business purposes - such as to process your everyday transactions, maintain your account(s), respond to court orders and legal investigations, or report to credit bureaus. [Does Citizens Bank share?] Yes [Can you limit this sharing?] | No | [
[
"N",
"o"
],
[
"W",
"e",
" ",
"d",
"o",
"n",
"'",
"t",
" ",
"s",
"h",
"a",
"r",
"e"
]
] | Citizens Bank Privacy Policy | Can you limit this sharing? | http://www.gocitizensbank.com/FinancialPolicy.html | 48/1438042987775.70_20150728002307-00301-ip-10-236-191-2_479384530_6.json |
6ffaece7_Citizens_Bank_Privacy_Policy__Can_you_limit_this_sharing_ | For our marketing purposes - to offer our products and services to you. [Does Citizens Bank share?] No [Can you limit this sharing?] | We don't share | [
[
"N",
"o"
],
[
"W",
"e",
" ",
"d",
"o",
"n",
"'",
"t",
" ",
"s",
"h",
"a",
"r",
"e"
]
] | Citizens Bank Privacy Policy | Can you limit this sharing? | http://www.gocitizensbank.com/FinancialPolicy.html | 48/1438042987775.70_20150728002307-00301-ip-10-236-191-2_479384530_6.json |
6ffaece7_Citizens_Bank_Privacy_Policy__Can_you_limit_this_sharing_ | For joint marketing with other financial companies [Does Citizens Bank share?] Yes [Can you limit this sharing?] | No | [
[
"N",
"o"
],
[
"W",
"e",
" ",
"d",
"o",
"n",
"'",
"t",
" ",
"s",
"h",
"a",
"r",
"e"
]
] | Citizens Bank Privacy Policy | Can you limit this sharing? | http://www.gocitizensbank.com/FinancialPolicy.html | 48/1438042987775.70_20150728002307-00301-ip-10-236-191-2_479384530_6.json |
6ffaece7_Citizens_Bank_Privacy_Policy__Can_you_limit_this_sharing_ | For our affiliates' everyday business purposes - information about your transactions and experiences. [Does Citizens Bank share?] No [Can you limit this sharing?] | We don't share | [
[
"N",
"o"
],
[
"W",
"e",
" ",
"d",
"o",
"n",
"'",
"t",
" ",
"s",
"h",
"a",
"r",
"e"
]
] | Citizens Bank Privacy Policy | Can you limit this sharing? | http://www.gocitizensbank.com/FinancialPolicy.html | 48/1438042987775.70_20150728002307-00301-ip-10-236-191-2_479384530_6.json |
6ffaece7_Citizens_Bank_Privacy_Policy__Can_you_limit_this_sharing_ | For our affiliates' everyday business purposes - information about your creditworthiness. [Does Citizens Bank share?] No [Can you limit this sharing?] | We don't share | [
[
"N",
"o"
],
[
"W",
"e",
" ",
"d",
"o",
"n",
"'",
"t",
" ",
"s",
"h",
"a",
"r",
"e"
]
] | Citizens Bank Privacy Policy | Can you limit this sharing? | http://www.gocitizensbank.com/FinancialPolicy.html | 48/1438042987775.70_20150728002307-00301-ip-10-236-191-2_479384530_6.json |
6ffaece7_Citizens_Bank_Privacy_Policy__Can_you_limit_this_sharing_ | For nonaffiliates to market to you [Does Citizens Bank share?] No [Can you limit this sharing?] | We don't share | [
[
"N",
"o"
],
[
"W",
"e",
" ",
"d",
"o",
"n",
"'",
"t",
" ",
"s",
"h",
"a",
"r",
"e"
]
] | Citizens Bank Privacy Policy | Can you limit this sharing? | http://www.gocitizensbank.com/FinancialPolicy.html | 48/1438042987775.70_20150728002307-00301-ip-10-236-191-2_479384530_6.json |
7a3d05d2_poona_Quiz___By_psychopenguins__Hint | [My Thought] Orcalphin's Were Created by Mixing Dolphins With BP [Hint] | An Escape Pod Crashes Here And The Scenery Is Beautiful | [] | Opoona Quiz - By psychopenguins | Hint | http://www.sporcle.com/games/psychopenguins/Opoona | 49/1438042988962.66_20150728002308-00020-ip-10-236-191-2_729071196_2.json |
7a3d05d2_poona_Quiz___By_psychopenguins__Hint | [My Thought] Wild Parties In the Apartment With My Dawg G-Bone [Hint] | Where Opoona Gets His First Attendant Job | [] | Opoona Quiz - By psychopenguins | Hint | http://www.sporcle.com/games/psychopenguins/Opoona | 49/1438042988962.66_20150728002308-00020-ip-10-236-191-2_729071196_2.json |
7a3d05d2_poona_Quiz___By_psychopenguins__Hint | [My Thought] And Opoona Falls For Joey's Trick For The 24th Time In A Row! Yay More Walking! [Hint] | A Village With An Elevator In The Middle Of The Ground | [] | Opoona Quiz - By psychopenguins | Hint | http://www.sporcle.com/games/psychopenguins/Opoona | 49/1438042988962.66_20150728002308-00020-ip-10-236-191-2_729071196_2.json |
7a3d05d2_poona_Quiz___By_psychopenguins__Hint | [My Thought] Boise State's Summer Getaway [Hint] | What Location Has An Awesome Clubhouse Area On The Top Floor | [] | Opoona Quiz - By psychopenguins | Hint | http://www.sporcle.com/games/psychopenguins/Opoona | 49/1438042988962.66_20150728002308-00020-ip-10-236-191-2_729071196_2.json |
7a3d05d2_poona_Quiz___By_psychopenguins__Hint | [My Thought] Triple Rainbow All Da Way! [Hint] | Location Between Paradiso And Great Dunes East | [] | Opoona Quiz - By psychopenguins | Hint | http://www.sporcle.com/games/psychopenguins/Opoona | 49/1438042988962.66_20150728002308-00020-ip-10-236-191-2_729071196_2.json |
7a3d05d2_poona_Quiz___By_psychopenguins__Hint | [My Thought] No Comment [Hint] | Rikhael Loses His Love, But What is Her Name? | [] | Opoona Quiz - By psychopenguins | Hint | http://www.sporcle.com/games/psychopenguins/Opoona | 49/1438042988962.66_20150728002308-00020-ip-10-236-191-2_729071196_2.json |
7a3d05d2_poona_Quiz___By_psychopenguins__Hint | [My Thought] If You Got That You Have Issues [Hint] | What Appears Where A Name Should Be During Conversations With Random Characters? | [] | Opoona Quiz - By psychopenguins | Hint | http://www.sporcle.com/games/psychopenguins/Opoona | 49/1438042988962.66_20150728002308-00020-ip-10-236-191-2_729071196_2.json |
7a3d05d2_poona_Quiz___By_psychopenguins__Hint | [My Thought] I Think The Joke Is In The Answer [Hint] | What is Artiela's Gambling Location Called? | [] | Opoona Quiz - By psychopenguins | Hint | http://www.sporcle.com/games/psychopenguins/Opoona | 49/1438042988962.66_20150728002308-00020-ip-10-236-191-2_729071196_2.json |
7a3d05d2_poona_Quiz___By_psychopenguins__Hint | [My Thought] Don't Worry Somehow Fireflies Can Cure It! Fireflies Can Cure Anything! [Hint] | What Disease Does Ted Have? | [] | Opoona Quiz - By psychopenguins | Hint | http://www.sporcle.com/games/psychopenguins/Opoona | 49/1438042988962.66_20150728002308-00020-ip-10-236-191-2_729071196_2.json |
7a3d05d2_poona_Quiz___By_psychopenguins__Hint | [My Thought] IT'S MINE ALL MINE! [Hint] | Where Is The Moon Forest Hotel Located? | [] | Opoona Quiz - By psychopenguins | Hint | http://www.sporcle.com/games/psychopenguins/Opoona | 49/1438042988962.66_20150728002308-00020-ip-10-236-191-2_729071196_2.json |
7a3d05d2_poona_Quiz___By_psychopenguins__Hint | [My Thought] It Definitely Looks Like Fat Everyday On The Sign. Just Sayin'. [Hint] | What Is The Fastfood Restaurant In Lifeborn Called? | [] | Opoona Quiz - By psychopenguins | Hint | http://www.sporcle.com/games/psychopenguins/Opoona | 49/1438042988962.66_20150728002308-00020-ip-10-236-191-2_729071196_2.json |
7a3d05d2_poona_Quiz___By_psychopenguins__Hint | [My Thought] Stacia=Paris Hilton [Hint] | Name One Person In The VIP Room in Lifeborn. | [] | Opoona Quiz - By psychopenguins | Hint | http://www.sporcle.com/games/psychopenguins/Opoona | 49/1438042988962.66_20150728002308-00020-ip-10-236-191-2_729071196_2.json |
7a3d05d2_poona_Quiz___By_psychopenguins__Hint | [My Thought] Oh Yeah, You Were All Feeling A Lot Better About 9 Questions Ago Weren't You? [Hint] | What Is Opoona's Apartment Number? | [] | Opoona Quiz - By psychopenguins | Hint | http://www.sporcle.com/games/psychopenguins/Opoona | 49/1438042988962.66_20150728002308-00020-ip-10-236-191-2_729071196_2.json |
7a3d05d2_poona_Quiz___By_psychopenguins__Hint | [My Thought] On A Side Note, The Girl In The Bikini In That Room Goes By The Name Of Fanny... I'm Sure That Was Unintentional. [Hint] | How Many Vehicles Are In Chariman Hope's First Floor Room? | [] | Opoona Quiz - By psychopenguins | Hint | http://www.sporcle.com/games/psychopenguins/Opoona | 49/1438042988962.66_20150728002308-00020-ip-10-236-191-2_729071196_2.json |
7a3d05d2_poona_Quiz___By_psychopenguins__Hint | [My Thought] I Thought I Would End It With An Easier Question. Unless You Got This Wrong, In Which Case It Wasn't An Easier Question. [Hint] | What Location Had The Volcano? | [] | Opoona Quiz - By psychopenguins | Hint | http://www.sporcle.com/games/psychopenguins/Opoona | 49/1438042988962.66_20150728002308-00020-ip-10-236-191-2_729071196_2.json |
55ffa01d_Daily_Telegraph_Tim_Blair_Blog__Most_Commented | [1] 75 [Most Commented] | CECIL BE DEMISED | [] | ZZ TOP! ZZ TOP! | Daily Telegraph Tim Blair Blog | Most Commented | http://blogs.news.com.au/dailytelegraph/timblair/index.php/dailytelegraph/comments/zz_top_zz_top/ | 5/1438042988718.8_20150728002308-00126-ip-10-236-191-2_34143285_8.json |
Subsets and Splits