<?xml version="1.0"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>Forums Tag: section</title>
<link>http://omeka.org/forums/</link>
<description>Forums Tag: section</description>
<language>en</language>
<pubDate>Sat, 11 Oct 2008 23:32:46 +0000</pubDate>

<item>
<title>KrisKelly on "Section names create unescaped characters"</title>
<link>http://omeka.org/forums/topic/section-names-create-unescaped-characters#post-211</link>
<pubDate>Thu, 06 Mar 2008 02:06:39 +0000</pubDate>
<dc:creator>KrisKelly</dc:creator>
<guid isPermaLink="false">211@http://omeka.org/forums/</guid>
<description>&#60;p&#62;Actually, disregard that last example, I haven't gotten the hang of using code examples on this forum yet.
&#60;/p&#62;</description>
</item>
<item>
<title>KrisKelly on "Section names create unescaped characters"</title>
<link>http://omeka.org/forums/topic/section-names-create-unescaped-characters#post-210</link>
<pubDate>Thu, 06 Mar 2008 02:05:50 +0000</pubDate>
<dc:creator>KrisKelly</dc:creator>
<guid isPermaLink="false">210@http://omeka.org/forums/</guid>
<description>&#60;p&#62;You're right, that is a bug, and thanks for catching it.  I've filed a bug report and it will be fixed in the next release.  For the moment though, I would try using curly quotes, since those won't trip up the browser when it parses the HTML.   Otherwise, you can avoid using quotes for titles of sections in the immediate future.&#60;/p&#62;
&#60;p&#62;As to allowable characters, I get that you're talking about how Omeka converts some characters to the HTML entities but leaves others intact.  When writing templates for Omeka, it's generally a good idea to enter the text rather than the HTML entities representation (e.g. use curly quotes rather than typing &#38;#8212;, &#38;#38; instead of &#38;amp; etc.).  There is a templating helper function called h() that is used throughout omeka which will take care of making sure the HTML output is valid.  In most cases this is a synonym for php's built-in &#60;a href=&#34;http://us2.php.net/htmlentities&#34;&#62;htmlentities()&#60;/a&#62; function, but it also allows you to mix HTML tags in your data entry, so in most cases you could enter the following into Omeka:&#60;/p&#62;
&#60;p&#62;&#60;code&#62;&#60;em&#62;Cookies&#60;/em&#62; &#38;#38; Cream&#60;/code&#62;&#60;/p&#62;
&#60;p&#62;And it would spit out:&#60;/p&#62;
&#60;p&#62;&#60;code&#62;&#60;em&#62;Cookies&#60;/em&#62; &#38;amp; Cream&#60;/code&#62;&#60;/p&#62;
&#60;p&#62;Hope that helps.
&#60;/p&#62;</description>
</item>
<item>
<title>KerriHicks on "Section names create unescaped characters"</title>
<link>http://omeka.org/forums/topic/section-names-create-unescaped-characters#post-200</link>
<pubDate>Tue, 04 Mar 2008 19:33:18 +0000</pubDate>
<dc:creator>KerriHicks</dc:creator>
<guid isPermaLink="false">200@http://omeka.org/forums/</guid>
<description>&#60;p&#62;One of my users is working on an exhibit, and she created a section that was also the title of an article. As such, she put the section title in quotation marks.&#60;/p&#62;
&#60;p&#62;Omeka brought those quotation marks into the markup, creating an HTML link to the section that contained unescaped quotation marks. Of course, this rendered the link unusable, and no one was able to get access to that section. I'm thinking this is a bug that needs addressing.&#60;/p&#62;
&#60;p&#62;In the meantime, I could suggest that she use character entities for the quotation marks, but it looks like Omeka does, in fact, digest certain punctuation characters and rewrite them. Is there a list anywhere of allowable characters?&#60;/p&#62;
&#60;p&#62;Any advice?&#60;/p&#62;
&#60;p&#62;--Kerri
&#60;/p&#62;</description>
</item>
<item>
<title>DaveLester on "Unable to add text without image to exhibit section pages"</title>
<link>http://omeka.org/forums/topic/unable-to-add-text-without-image-to-exhibit-section-pages#post-124</link>
<pubDate>Thu, 31 Jan 2008 16:40:15 +0000</pubDate>
<dc:creator>DaveLester</dc:creator>
<guid isPermaLink="false">124@http://omeka.org/forums/</guid>
<description>&#60;p&#62;In regard to your last question, could you provide a bit more context of when you're observing this discrepancy in ordering exhibit pages?  Did you delete an exhibit page at some point?
&#60;/p&#62;</description>
</item>
<item>
<title>DouglasKnox on "Unable to add text without image to exhibit section pages"</title>
<link>http://omeka.org/forums/topic/unable-to-add-text-without-image-to-exhibit-section-pages#post-96</link>
<pubDate>Thu, 17 Jan 2008 18:20:37 +0000</pubDate>
<dc:creator>DouglasKnox</dc:creator>
<guid isPermaLink="false">96@http://omeka.org/forums/</guid>
<description>&#60;p&#62;Thanks, maybe this is a result of the same issue, but somehow my exhibit pages have been able to skip page sequence.  I have an exhibit with pages in order &#34;1, 2, 4, 5.&#34;
&#60;/p&#62;</description>
</item>
<item>
<title>JeremyBoggs on "Unable to add text without image to exhibit section pages"</title>
<link>http://omeka.org/forums/topic/unable-to-add-text-without-image-to-exhibit-section-pages#post-92</link>
<pubDate>Mon, 07 Jan 2008 21:33:27 +0000</pubDate>
<dc:creator>JeremyBoggs</dc:creator>
<guid isPermaLink="false">92@http://omeka.org/forums/</guid>
<description>&#60;p&#62;Hi Douglas,&#60;/p&#62;
&#60;p&#62;This is a bug with RC4, and you're the first to catch it. We've added it to our list of tickets to complete before the public release. At the moment, there isn't an easy fix for this for RC4, but rest assured we'll have it fixed before the public release.&#60;/p&#62;
&#60;p&#62;As far as your comment on the database structure is concerned: Right now the structure of the table for exhibit items/text (items_section_pages) does imply a relationship between items and text, for a table in that record. But, the table is set up so that the item_id field in that table can have a NULL value. So, a record in this table doesn't need an item associated with it. A text field can stand alone in a page layout, though there seems to be a bug displaying the text input through the &#34;Text&#34; layout.
&#60;/p&#62;</description>
</item>
<item>
<title>SheilaBrennan on "Unable to add text without image to exhibit section pages"</title>
<link>http://omeka.org/forums/topic/unable-to-add-text-without-image-to-exhibit-section-pages#post-91</link>
<pubDate>Sun, 06 Jan 2008 16:05:50 +0000</pubDate>
<dc:creator>SheilaBrennan</dc:creator>
<guid isPermaLink="false">91@http://omeka.org/forums/</guid>
<description>&#60;p&#62;Hi Douglas, &#60;/p&#62;
&#60;p&#62;We're trying to replicate the problem you had with creating text-only layouts in the exhibit builder.  You should be able to create text-only exhibit pages. We are doing that on a project in-progress here at CHNM where image-free essays are published online using the exhibit function. But we are investigating whether we have missed something. &#60;/p&#62;
&#60;p&#62;We have designed Omeka so that you may write and publish exhibit section descriptions as well. The pages serve as subsections, where you place items (if you choose them) in context or offer a longer piece of exhibit text. Then individual item descriptions and their metadata fields can act like traditional object labels.&#60;/p&#62;
&#60;p&#62;At the item level, you can also create a text-only item that does not contain a file. For instance, when you add an item to the archive, choose the Document type. In Step 1, there is a field for &#34;text&#34; (such as text from a primary source) that can hold text with or without an accompanying file. In that case the item description offers a summary of that text.&#60;/p&#62;
&#60;p&#62;We plan to create additional exhibit page layouts, so if you have other suggestions please let us know.
&#60;/p&#62;</description>
</item>
<item>
<title>DouglasKnox on "Unable to add text without image to exhibit section pages"</title>
<link>http://omeka.org/forums/topic/unable-to-add-text-without-image-to-exhibit-section-pages#post-87</link>
<pubDate>Fri, 04 Jan 2008 17:55:31 +0000</pubDate>
<dc:creator>DouglasKnox</dc:creator>
<guid isPermaLink="false">87@http://omeka.org/forums/</guid>
<description>&#60;p&#62;I have just started trying out Omeka and have created a number of section pages for an exhibit, but am unable to create an exhibit section page consisting of just text without an item. There is a layout that is plain text, and the database table omeka_items_section_pages seems to allow item_id to be null, which suggests that I should be able to have an image-free section page. Is this a bug?&#60;/p&#62;
&#60;p&#62;The database structure makes me wonder about the assumptions of the data model. I can appreciate having a model where text can be attached to particular items in an exhibit context, but some pieces of text might have a different role, serving as section or subsection labels. Is it not the right way to think about how to use Omeka?
&#60;/p&#62;</description>
</item>

</channel>
</rss>
