Anonymous product information case study

Making structured product-information updates safer for nontechnical users

A product-development organization needed to stop retyping emailed spreadsheets and documents into its enterprise database while preserving a familiar document-based way of working.

  • Product Information
  • XML
  • XPath
  • JavaScript
  • Validation

The situation

Product descriptions moved through familiar office files, but every database update required error-prone retyping.

End users created and updated product information by emailing spreadsheets and word-processing documents. When the data was ready for the enterprise system, IT staff had to re-enter it into the database.

The client wanted to keep descriptions portable enough to email, save, compare, version, and share while constraining user choices so the structured result remained valid.

Illustrative product-information editor with structured fields, XML, validation, comparison, version saving, and sharing.
Illustrative structured product-information editor; not a production screenshot.

The challenge

Hide XML complexity without losing the structure that made updates dependable.

The editor needed to guide nontechnical users while remaining flexible as enterprise object properties changed.

01

Unstable property sets

Property names and ordering were not final, so a rigid form would be difficult to maintain.

02

Structured validation

Users needed constrained choices and a simple interface rather than direct XML editing.

03

Portable product documents

Descriptions had to remain independent enough to email, compare, version, and schedule before database import.

The solution

A guided editor turned enterprise object descriptions into valid, portable XML documents.

The client interface could open, create, edit, and save structured descriptions without asking end users to work directly with markup.

  1. 01

    Separate interface from object logic

    Define enterprise entity behavior in reusable JavaScript interfaces and implement it in focused entity classes.

  2. 02

    Match flexible structures

    Use XPath expressions to locate properties even when element names and order could change.

  3. 03

    Decouple updates from the database

    Treat product descriptions as documents that could be saved, emailed, compared, versioned, and scheduled for later import.

How we worked

Design for changing structures rather than hard-code the first property set.

The team first studied the cross-platform component environment supporting the user interface.

Object-oriented JavaScript kept enterprise entity contracts separate from individual implementations.

XPath literals were extracted into reusable constants so property matching could evolve without scattering fragile assumptions throughout the interface.

01Model

Define enterprise objects and reusable interface behavior.

02Guide

Present constrained fields instead of raw XML.

03Validate

Use XPath to match changing properties safely.

04Share

Save descriptions as portable, versionable documents.

The result

Product information became easier to prepare, validate, compare, and reuse without direct database work.

The documented application gave nontechnical users a guided interface while preserving the structured documents IT needed for dependable enterprise updates.

No database retypingfor prepared product descriptions
Structured validationbehind a guided user interface
Portable updatesfor saving, comparing, and versioning

Safer user input

Constrained fields reduced the need for nontechnical staff to understand XML structure.

More flexible maintenance

XPath-based matching accommodated changes in property names and order.

Decoupled scheduling

Descriptions could move through review and version control before the enterprise database was updated.

Case taxonomy

Searchable by industry, technology, product, and business need.

Industry and product

  • Business Software
  • Product Information Management
  • Structured Documents
  • Cross-platform Application

Technology and delivery

  • XML
  • XPath
  • JavaScript
  • XUL
  • XPCOM
  • Object-oriented Design

Business need

  • Validation
  • Document Comparison
  • Version Control
  • Database Decoupling
  • Nontechnical Users

Make structured data easier to maintain

Need a safer way for business users to prepare complex product information?

Talk to our team

Get in touch

Ready to build software that fits your business?

Tell us what you need to build, modernize, automate, or augment with AI. We can start with a focused discussion or a no-risk 1-week trial.

“A fantastic company to work with.” After the initial rapid development project, American Shipping Co. kept two Shinetech developers embedded for nearly four years, supporting internal and external tools and new AI initiatives.
Marc Greenberg testimonial portrait Marc GreenbergCEO, American Shipping Co. - 5-star Google Review

Response within 1 business day.