Our interactive card feature within our web data platform

We introduce our card feature which resides within our Web Data Platform. Our audience will come to see how we put a lot of effort into reducing complexity and opening the website up to more ways to push content and data to it.

You can see our example here www.inforhino.co.uk/company

Typical challenges with Website Content Management Systems and how Info Rhino solves them

Our Web Data Platform takes an entirely fresh approach to how data and content are maintained and presented to a website. Content Management Systems allow non-technical individuals to manage website content. Skilled practitioners in website development can maximise content management systems to make powerful enhancements to the website more than non-techies.

There are some major challenges to Website CMS platforms (WCMS);

• Maintaining content requires training in the WCMS and is a skilled job.
• Providing access to many staff can cause issues with controlling content quality.
• Rogue staff can cause significant damage to the website.
• Often, staff take information and reports from internal systems before manually transferring them to the WCMS - this is more likely to leave content due to the burden of maintaining the information.

To summarise, despite the incredible versatility of WCMS, the burden of maintaining the website is arduous and fraught with risk. Indeed, we haven't touched on many of the challenges we see clients face.

Thinking about the real benefit of content cards within our Web Data Platform

As a data analyst/reporting developer, we could write queries to export data and images to this folder structure. SQL Server contains a FOR JSON clause. Images can be exported from databases using a variety of methods. The images may reside on a directory of course. This content can be automatically published to the website folder. We could have Company staff structure, product lists, office locations, properties, clients, all exported to a folder available for automatic display to the Web Data Platform by a reporting team.

For our existing Info Rhino implementation, we manually created this structure and perhaps this can be a little fiddly but a front-end will be put together relatively easily.

The Info Rhino vision of content and websites

We took a 1000ft view, and asked - what are we trying to achieve? Originally, operating purely as a data consultancy, site-based for enterprise clients, we delivered data solutions and applications. We saw a common challenge, many of the tasks were about moving information from one system to another, transforming it, and always transforming configuration. Can we make information portability easier? Can experts focus on their jobs and reduce their workload? This was the driving force between our card feature - simple in implementation, yet only available in Enterprise Intranet technology such as SharePoint, without the continual configuration.

Our vision is to permit delivery of data and content to appropriate folders and allow our platform to display this content.

An example card file

[

{

"Title": "Child",

"Caption": "Draws pictures",

"Text": "Leo vel orci porta non pulvinar. Molestie nunc non blandit massa enim nec dui. Phasellus vestibulum lorem sed risus ultricies tristique nulla. Adipiscing at in tellus integer feugiat scelerisque varius morbi.",

"Link": null

},

{

"Title": "Child In Forest By Tree",

"Caption": "Sitting down on a log.",

"Text": "Justo nec ultrices dui sapien. Consectetur adipiscing elit duis tristique sollicitudin. Natoque penatibus et magnis dis parturient montes.",

"Link": null

},

{

"Title": "Bear And Fox",

"Caption": "In the forest",

"Text": "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Varius sit amet mattis vulputate enim nulla aliquet porttitor.",

"Link": null

}
]

The above file contains a flat set of rows which is self-explanatory. The really interesting thing is our Card Retriever will match each any image in the same folder matching the title and include that as a card image. Suddenly, we can create simple content and include a picture to provide a neat way to improve the look of the cards. We plan to extend this feature for different use cases.

Domains, Entities, and Topics - Levels within our cards feature

(insert image of cardfolder sample)

Many websites focus on three clicks access to all content for usability. Rules are there to be broken but we felt three levels with the ability to have cards at every level is a great way to decide what information to include at each level. The only real rule is we must have card content at the topic level.

Within the Topic folder, we have a DomainConfig.json file which helps us give more meaningful names to each level.

[

{

"DomainLevel" : "Domain"

,"Value" : "Organisation"

}

,

{

"DomainLevel" : "Entity"

,"Value" : "Sales Products"

}

, {

"DomainLevel" : "Topic"

,"Value" : "Product Items"

}

]

The domain root structure shows how easy it is to set up folders for entirely different domains.