Michael K. Bergman wrote: > David, > > Massively cool; I should have paid closer attention to this thread about > 1 month ago. Thanks. > > However, of course, I don't (does anyone?) want to simply post up a > static version of a dynamic exhibit solely to get indexed by search > engines. Somehow that feels like too much duplication. > Not really. It also provides a good way to let people without javascript view your data. This is what I have done with my exhibit. I thought about which of many presentations of the info would work best for a static page and used that one.
I posted a question earlier which I will repeat here: it seems that the <noscript> tag offers just the right way to make this happen. Is anyone aware of reasons to prefer the javascript hacks that delete the static content if javascript is enabled? eg, are the browsers that ignore <noscript>? > What I did on my web site was to have the full Exhibit version with > sortable and filterable records, and then to create a separate static > page with a simple table with live links as a kind of table of contents. > Other layout distinctions are possible between the static and dynamic > versions, but I do think different layouts help preserve respect for the > user by providing a different access/view/display option. > > What I did on my actual site was to modify the starting spreadsheet to > create these two versions, the dynamic Exhibit one fed directly from > Google, the other smaller version cut-and-pasted into the static HTML. > > But, with Copy All, there are some additional and cooler options. I > tried both with these strengths/trade-offs: > > 1. Generate HTML preserves all of the record info. With a few global > S&Rs, I was easily able to style="display: none" to select which info > actually displays, and then make some minor changes to format > differently (if, say, a more table listing view is desired). > *Advantage:* preserves all content for indexing *Disadvantage:* takes > some HTML manipulation and time > > 2. Generate a TSV file, import into Excel, remove columns with > undesired fields, embed into static page. *Advantage:* fast and avoids > Excel's crappy HTML/XML generation *Disadvantage:* some record content > not indexed. > > While it would be helpful for my specific needs to request a feature > that would allow individual data types to be selected for inclusion or > not when doing a Copy All, I actually think that would clutter Exhibit > and undercut its clean purpose. (Though I could foresee a separate > utility down the road that could do Exhibit-related manipulations or > processing. :)) > there has been some discussion of "copy all" having, as one of its output formats "static html representation" or even "whole web page containing both the exhibit and its static representation which you can just save on your site". > Bottom line: what is there is very cool, and there is flexibility to > the author to go multiple directions. > > Let me know if this portion is getting close to frozen, and I'll draft > up some documentation for the wiki. > > Thanks, Mike > > > > David Huynh wrote: > >> Hi Michael, >> >> You could go to your exhibit, scroll to the bottom, click "Show all 500 >> items", scroll to the top, click Copy All, and choose "Generated HTML of >> this View"... Let me know if that works for you and does what you want... >> >> David >> >> Michael K. Bergman wrote: >> >>> About 1/3 of the way into this thread about two months ago I made my >>> last comment and then promised I would refrain from further bandwidth >>> consumption. I was following Stefano's wise counsel of >>> draft-delete-think. :) >>> >>> However, the reason for DavidH to start this thread in the first place >>> remains. I just posted up a big update of my semantic tools listing >>> using Exhibit, which gets a fair amount of traffic that I'd like Google >>> to sustain. >>> >>> My answer (a kludge, really) to the indexing problem was to create a >>> simple parallel table page with links and, as I had recommended in >>> earlier posts, an adequate intro paragraph describing the nature of the >>> exhibit on the Exhibit page itself. >>> >>> It would be great to have this parallel entry be able to be created >>> through some Exhibit code or function, but actually what I did by hand >>> was not too terrible (though an inelegant hack if one has greater skills!). >>> >>> As a stop gap until better options emerge, I'd still be happy to write >>> up a temporary placeholder on the Simile wiki for this approach. (But I >>> feel reluctant cluttering *real* new substance to the wiki without a >>> sense it is valuable to the community.) >>> >>> Thoughts? >>> >>> Thanks, Mike >>> >>> >>> _______________________________________________ >>> General mailing list >>> [email protected] >>> http://simile.mit.edu/mailman/listinfo/general >>> >>> >> _______________________________________________ >> General mailing list >> [email protected] >> http://simile.mit.edu/mailman/listinfo/general >> >> > > _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
