Datalynx Tags

Datalynx tags are special patterns used in the view settings as a placeholder. These tags inserted in the settings will then be replaced in the view with dynamically created data.

Example 1: The tag ##author:firstname##, is placed in the view setting "entry template". The user "Micheal Mulley" creates a new entry. The owner of this entry is Micheal Mulley. Viewing the entry will now display "Micheal" in the exact place the tag ##author:firstname## was set in the "view settings". The firstname of the author is taken from the users profile field.

Example 2: The tag [[my favourite film]] is placed in the "entry template" settings of a view. Before the field "my favourite film" was created in "Manage -> Fields" (type: text). The user clicks on the button "Add new entry" in the default view. A form will open, where the user can enter his/her favourite film in a form, at the exact place where [[my favourite film]] was put in the view settings "entry template".

Datalynx tag types

There are different types of datalynx tags. They can be divided into "where they can be placed" and "what data can be manipulated".

• Datalynx field tags: These tags will display the value of a field, in an entry. In editing mode they will show a form element, that is used for data input. Datalynx field tags can only be used in the "entry template" section in the settings of a view.
  • Patterns of a datalynx field tag: This is the pattern used in the view settings as a placeholder
    • [[fieldname]] This will display the value of a field in an entr
    • [[fieldname@]] This will display the content of the "field label", which itself includes a conditional text (that means for example a description of the field and the field value itself. If the field value is empty, the field label will not be shown at all). For a detailed explanation of the field label have a look at [[Datalynx Fields|Fields]
• Datalynx entry tags: TBC

Datalynx tag locations

There are 2 main locations in where to put tags, and some other rare usecases. The main locations are in the settings of a view "view template" and "entry template"

• View template: These tags have the following propertie
  • They do not handle data of a single entr
  • They do not handle data of a single use
  • They handle data of general view properties: Example: ##quicksearch## provides a search field for entering keywords to search all entries
• Entry template
  • User data relevant for a single entry. Example: ##author:lastname## displays the last name of the author of an entry in the entry itself
  • Entry properties relevant for a single entry. Example: the id of an entry ##entryid###
  • Field tags. These tags are used to display and edit different types of data in a single entry. Example: [[duration]] will display a duration. The field has to be defined in "Manage -> Fields" prior to be used in a view. In this case the field is of the type "duration".
  • Other tags: These include action tags for approving entries, or comment tags for commenting or rating tags
• Other locations
  • Within tags. Example: A tag for creating a download link in order to download a PDF, can include the entry id of an entry, that should be exported as PDF
  • Special view settings: In the PDF view there is a possibility to define the name of a PDF. Tags like ##author:lastname## can be used to dynamically create the filename

List of tags

Tag	Description	Example /Result	Locations
##viewurl##	The url of the current view	http://www.example.com/mod/datalynx/view.php?d=3&view=4	View template, entry template
##viewurl:view-name##	The url of a view with the name view-name in the current datalynx.view-name: The name of view that is linked.link-text: The text of the link. Could be html but ';' or any html special chars that would contain ';' if entered in editor mode, cannot be used. A special link-text pattern allows for display theme icons, e.g. _pixicon:f/pdf:Download, _pixicon:i/edit:Edit etc.url-query: Url query parameters that will be added to the view url in the link. These are arg=val pairs separated by |. The args should be expected by the target view to take effect. The vals can be entry patterns.	#{{viewlink:Certificate;_pixicon:f/pdf:Download;pdfexportentry=##entryid##|dest=D|docname=[[CertID]]-[[CertYear]][[CertMonth]];}}#	Entry template
#{{viewlink:view-name;link-text;url-query;}}#	View link for each of the datalynx views.		Entry template
#{{viewsesslink:view-name;link-text;url-query;}}#	Like the above but with session key added to the url.	#{{viewsesslink:Single;_pixicon:i/edit:Edit;editentries=##entryid##;}}#This pattern added to an entry template will display a linked edit icon to a view called Single and will open the entry in edit mode in that view.	Entry template
##approve##			Entry template
##edit##			Entry template
##delete##			Entry template
##select##			Entry template
##export##			Entry template
##duplicate##			Entry template
##status##			Entry template
##comments##			Entry template
##comments:count##			Entry template
##comments:inline##			Entry template
##anchor##			Entry template
##more##			Entry template
##moreurl##			Entry template
##entryid##			Entry template
##group:id##			Entry template
##group:name##			Entry template
##group:picture##			Entry template
##group:edit##			Entry template
##ratings:rate##			Entry template
##ratings:view##			Entry template
##ratings:viewinline##			Entry template
##ratings:avg##			Entry template
##ratings:count##			Entry template
##ratings:max##			Entry template
##ratings:min##			Entry template
##ratings:sum##			Entry template
##author:id##			Entry template
##author:name##			Entry template
##author:edit##			Entry template
##author:firstname##			Entry template
##author:lastname##			Entry template
##author:username##			Entry template
##author:idnumber##			Entry template
##author:picture##			Entry template
##author:picturelarge##			Entry template
##author:email##			Entry template
##numentriestotal##
##numentriesdisplayed##
##viewurl##
##viewsmenu##
##filtersmenu##
##quicksearch##
##quickperpage##
##advancedfilter##
##addnewentry##
##addnewentries##
##selectallnone##
##multiduplicate##
##multiduplicate:icon##
##multiedit##
##multiedit:icon##
##multidelete##
##multidelete:icon##
##multiapprove##
##multiapprove:icon##
##multiexport##
##multiexport:icon##
##multiimport##
##multiimporty:icon##
##pagingbar##