We know page rank algorithm is the random surfer, which can browse hyperlinks or do random teleports. Lets imagine a scenario where we want to extend this where consider the option for the random surfer to use a "back button of the browser" which takes him to the back page (i.e page where he came from. However, the random surfer is not allowed to use this option recursively. So, once he used back button he has to either click a link or teleport to new page. Furthermore, we consider back button to be used with certain probability 'p'.
Note: we have to restrict user not to use back button recursively.
I was wondering how can we extend the existing page rank algorithm where a user can go from one page to next page with probability (1/number of outlinks) or teleport with probability alpha.
Any idea or link for further reading would be appreciated. I tried to google "pagerank with backlink" but couldn't find good information.
PageRank relies on links between pages. Clicking on the back button is not creating a link between pages. So if you go from page A to page B, there isn't necessarily a link from B to A.
You could add them to your graph or adjust the probability if they already exist and re-run PageRank.
Related
I am doing a site in Wix.com so my wife can maintain it without my input. The draft site is live at:
http://www.wingspan.info
IMPORTANT: The wife is not a techie.
Essentially, the site displays our art work in galleries of paintings, etc, filtered by artist.
I have coded one page, then duplicated that to create the galleries and filter the WixDataQuery according to Andrew or Helen and Categories like Painting, Drawing, Sculpture, iPad Art, etc. Also, where we have exhibited (Exhibitions menu) some of our paintings.
All working, but any change to design and I have to change 15 pages...
So, it now strikes me that it would be more efficient to design one dynamic page, and set up the menu to display the different categories, as it is set up in the live site:
However, I can't find any documentation that shows how to use just the one dynamic page rather than my coded page duplicated to produce 12 different pages. Not clever...
Any suggestions / tutorials where I can find how to do this?
Thanks!
Basically, you want to add the Content Manager to your site if you haven't already, and then set up a collection with all of your data in it. One row per eventual "page" that you want.
Next, you can take the page you already designed and convert it to a dynamic page. It will then have a dataset on the page which you need to connect to various elements on the page through their connect buttons.
Finally, you'll need to edit your menu to point to the various instances of your dynamic page instead of the regular pages you have them pointing to now.
You can read all about how dynamic pages work here and here.
I am trying to create a site with high rankings in accessibility and one of the things i have come across is. My live search (that makes a ajax request and shows suggestions from what you type in the search bar on "keyup").
The list of suggestions i full of links that will take you to the page you are looking for meaning there is no submit page containing your results you just click the links therefore a submit button would be in my opinion redundant and useless.
My question therefore: Is it possible to make a form ex a live search without a submit button without the site being ranked lower than if it had a search button?
Is it possible to make a form ex a live search without a submit button without the site being ranked lower than if it had a search button?
You have to read WCAG Success Criterion 3.2.2 On Input
The first technique proposed is G80: Providing a submit button to initiate a change of context
But there's another technique which would not require a submit button:
G13: Describing what will happen before a change to a form control that causes a change of context to occur is made
TLDR: yes, but.
Its usually considered good practice to have a 'fallback' scenario. Say, for instance, the user is not using JS (god forbid) or if the user is using a screen reader of some sort - the search box should direct the user to a new page with listed results.
A helpful guide to building accessible sites can be found at (https://www.w3.org)[https://www.w3.org/TR/WCAG20-TECHS/]
I was wondering if we have to consider interactive elements of a web page which are basically changing a section of a web page as a new level when making a site map. For example, I have a web page "x" with edit, new, delete function button. Clicking on these buttons changes only a specific part of the page which is associated which is a constant area in itself. The parts of the web pages which don't change are the top navigation, footer etc. While thinking of a site map I wasn't sure if clicking on features like edit would be considered a new level since the web page is the same.
No, interactive page elements would not be considered part of a site map.
The page they reside on would be placed on the site map, but that is it.
A site map is meant to record the hierarchy and individual pages of a site... the things a person can navigate to.
Interactive elements would not fit this unless there are several different bits on one page and those bits can be reached by anchors.
My team is designing a set of applications, some of them are using trees to display data. The levels of the trees are 2-4 at the moment, might grow later depending on our domain model.
Lets say that we have 3 levels:
Book
Page
Word
My question is this: What would you, as a user, expect to see in a context menu on the nodes on the different levels?
Example Book context menu:
New Page
New Book
Edit Book
Delete Book
Example Page context menu:
New Word
Edit Page
Delete Page
Example Word context menu:
Edit Word
Delete Word
(I don't care about separators for now)
The thought about this example setup is that you edit the node you clicked on.
Inserting a new Word edits the Page you clicked on.
Only exception is the root node, where you can actually create a new root node.
All input is welcome an appreciated.
Edit:
I'm thinking, is this the right setup of the CRUD operations, or would you expect to see a Add Page in the context menu for a Page node?
Listing a few below which come to my mind -
Refresh
Move
Rename
There could be more based upon what operations can be done on the items as per the functionality in your application. Best thing is to ask the customer\business ambassadors and
build only what is needed.
Edit:
IMO, Add Page should be available only on the Book element.
I have a tree representation of pages in a CMS application. I understand how to persist the tree in the database. However, I don't have a good way to:
A) Reorder subpages under a particular parent page.
B) Provide a UI implementation that allows the user to change the order.
Any suggestions?
Changing the order itself will require you store some sort of ordering along with each page in the database. Just the current highest / lowest value +/- 1 would probably be a fine starting point. Once you've got that ordering in there, reordering becomes a case of swapping two values or changing the value for one page to be between two others (you could use floats I guess, but you may need to renumber if you split it too many times).
Anyway, once you've got that, you need a UI. I've seen a very simple 'swap this with the one above/below' approach which can be a simple web link or an AJAX call. You could also present all the page values to the user and ask them to renumber them as they see fit. If you want to get fancy, JavaScript drag and drop might be a good approach. I've used ExtJS and Mootools as frameworks in this kind of area. If you don't need all the Extjs widgets, I'd say well away from it in future, and look at something like the Mootools Dynamic Sortables demo.
A) I have a similar CMS app and I store an ordinal value with the page for a particular tree and sort on this value -- because lots of my pages appear in completely different sites I have to maintain the ordinal number against a page / tree combination.
B) I too would like a better way to do this. Currently they click on the node in the treeview and in the main page screen they can move the page around. I've tried drag and drop with java script and other solutions but my users could never work with it without lots of hand holding. I'll be interested in the responses to this one.