4,497
edits
FamilySearch Wiki:WikiProject Integrating Place Standards Database with FamilySearch Wiki: Difference between revisions
FamilySearch Wiki:WikiProject Integrating Place Standards Database with FamilySearch Wiki (view source)
Revision as of 12:25, 24 March 2009
, 24 March 2009no edit summary
No edit summary |
No edit summary |
||
| Line 17: | Line 17: | ||
=== Making titles readable by both humans and the standards database === | === Making titles readable by both humans and the standards database === | ||
We need to modify the extension and/or the skin to show a human-readable title while hiding the "Place:" and the numerical ID. Using namespace to do this is problemmatical: If we include this new namespace in the title, it confuses customers. If the namespace on the title is not displayed, users will not realize why search isn't finding an article (because it's in a namespace which isn't searched by default.) Our leaning now is to make the title of the page be what's in the "full name" field in the authorities form.<br> | We need to modify the extension and/or the skin to show a human-readable title while hiding the "Place:" and the numerical ID. Using namespace to do this is problemmatical: If we include this new namespace in the title, it confuses customers. If the namespace on the title is not displayed, users will not realize why search isn't finding an article (because it's in a namespace which isn't searched by default.) Our leaning now is to make the title of the page be what's in the "full name" field in the authorities form.<br> | ||
=== Don't create millions of stubs<br> === | === Don't create millions of stubs<br> === | ||
We don't want to create all the place pages at once as stubs which only contain the authority database data. | We don't want to create all the place pages at once as stubs which only contain the authority database data. | ||
=== Google and the wiki search engine need to see most data in standards database === | === Google and the wiki search engine need to see most data in standards database === | ||
Since all the data in the form appends the dbase but not the wiki, Google couldn't find it. We need updates to the authorities database to update the wiki as well. | Since all the data in the form appends the dbase but not the wiki, Google couldn't find it. We need updates to the authorities database to update the wiki as well. | ||
=== Extension needs to work with FCK === | === Extension needs to work with FCK === | ||
Test whether the extension which creates an info box is compatible with FCK. FCK breaks templates. The extension uses embedded template, so it might work. | Test whether the extension which creates an info box is compatible with FCK. FCK breaks templates. The extension uses embedded template, so it might work. | ||
== Issues to work out == | == Issues to work out == | ||
#When users add data to the fields, no data is added to the wiki. When data is added to the first half of the fields, data is written to the standards database. Additions to the second half of the fields would be submitted | #When users add data to the fields, no data is added to the wiki. When data is added to the first half of the fields, data is written to the standards database. Additions to the second half of the fields would be submitted. | ||
#Prevent variant names from displaying in the page, or display just the top 5 variants and have a "more" link that leads to the rest. | |||
#We need to decide which fields we want to display on a place page, and which data within each field we want to display. For instance, we might not want to list every cemetery in a county within the infobox, but we might want to list it on the content pane of the page in a box. | |||
#Should we include a boilerplate for the main content pane of a place page which has certain headings about a place? This way when a place page is generated, it doesn't contain only the place authorities data. | |||
<br> | <br> | ||