I'm having trouble writing a user story for a back-end process.
Let say you are building a website that sells widgets. You have a page on the site where your site visitors can see all the details of the widget - pictures, videos, and detailed specifications.
All widget details are sourced from a third party provider. There is a scheduled task that picks up an XML file with the widget specifications, and related images/video and imports these into your database.
I have to write some user stories that capture all of this.
I can think of a story such as "As a widget researcher I can view the pictures, videos, and specifications for a widget". This would cover the building of the actual web page to view the details of a particular widget.
We also need a story for the back-end process that populates the database with all the widget data. It could be a task of the story above, but then it would be too big - it's probably a sprint or two of work in it's own right. When trying to frame this import from a user perspective, I just end up with the same user story, i.e. "As a widget researcher I can view the pictures, videos, and specifications of a widget".
Is there an alternative wording I could use for the import, frame it from a user perspective, and prevent confusion between the story for the import and the story for building the page to view the data itself.