Formal Documents Museum Catalog - Library Catalog...

[tommythejoat]

We are considering making our museum available as an on-line resource. One of the issues beyond images and videos, etc. is the creation of a catalog that would replace the public interface of Past Perfect Online.

When we first started using VaultWiki over 10 years ago, we had a very serious user doing setup with template creation and a lot of category organization. He was unable to continue that work and the material is many versions old now.

Today I have been trying to repair an article that uses a template we call Book ref which uses parameters to create a formal reference to a book publication and similar ones for other references. In all cases those translate into footnotes (although they are not currently working). Those references are not really footnotes but bibliographic references.

I fount this template on this site: https://www.vaultwiki.org/pages/Temp...light=citation but it is not clear to me how it is supposed to work except it is very different from the template format we are currently using on our site.

Is there a bibliographic tool that will support a reference like (Moore, 1947) that links to a full citation in a bibliography section at the end of a document?

The template above sort of implies that we can freely use html in the context of a template.

[pegasus]

VaultWiki does not currently have a separate bibliographic tool. The current implementation relies on using templates that are designed and formatted based on the site's needs, or manually entering citation text into a FOOTNOTE tag (which helps generate a works-cited-like section). As you noted, the format of the footnote in context is not MLA or anything like that. We could consider improving that somehow.

Templates do not necessarily allow you to freely use HTML. They follow the same parsing rules of the area they are saved in. If the area allows HTML, then the template can contain HTML.

It is interesting that you bring this up though. I have been thinking a lot about citations recently myself.

Anyway, since you are trying to repair a particular template, maybe I can help. Specifically what is the issue you are encountering with your template?

[tommythejoat]

The template in question includes a footnote and puts the footnote in standard reference format. There is one for book references and another for articles. They use the parameter of the footnote as one of the arguments and then the author, title, publisher, date, etc.

When it is processed, the footnote that it generates appears in line as text. i.e. it is not parsed. This is the article I have been working on that uses the template ref book. https://mb.nawcc.org/wiki/Dennison-Aaron-Lufkin. Here is the link to the template itself in the system name space. https://mb.nawcc.org/wiki/Template:Ref-book.

My problem may be that the change in location of the templates has messed up the parsing also.

Grateful for any help you can give.

We are about to upgrade the site to XF2 with most of the work being done by Audentio. If we need some styling for the Encyclopedia, would you be able to help.

[pegasus]

The footnotes in that page that aren't parsing appear to be using a template called "foot book", which is intended to insert a FOOTNOTE BB-Code. However, the template has syntax like:

[footnote[if="{{{1}}}"]={{{1}}}[else /][/if]]

As you can see, the IF is attempting to modify the tag portion of the footnote (before the equals sign), rather than the option portion (after the equals sign). This may have worked years ago in vBulletin, but it conflicts with some security aspects, and is not possible at all in XenForo. I can't be sure that it is the only problem, but it definitely isn't helping.

You will want to place the IF on the outside of the footnote tag, with two copies, like:

[if="{{{1}}}"]
[footnote={{{1}}}] ... footnote content ... [/footnote]
[else /]
[footnote] ... footnote content ... [/footnote]
[/if]

To avoid duplicating the code inside the footnote tags, you can consider using local variables:

[var]set|footnoteContent| ... footnote content ...[/var]
...
[var]get|footnoteContent[/var]