Folios - Revision history

Stellent at 18:47, 25 May 2011

2011-05-25T18:47:15Z

← Older revision		Revision as of 18:47, 25 May 2011
Line 28:		Line 28:

	Be warned that Folios have some rough edges. One of them is that, a document is added to a Folio, then any of the above metadata fields are changed independently, those changes will not be reflected in the Folio.		Be warned that Folios have some rough edges. One of them is that, a document is added to a Folio, then any of the above metadata fields are changed independently, those changes will not be reflected in the Folio.
			=Folio Revisions=
			*Since Folios are stored as regular documents in the ICMS they can be revised.
			*To do this, when the folio is in edit mode select Actions > 'Create snapshot'. This will bring up the new revision for the Folio in edit mode. Select Actions > Save Changes to check in the new revision.

	=Simple Folios=		=Simple Folios=

Stellent at 18:41, 25 May 2011

2011-05-25T18:41:01Z

← Older revision		Revision as of 18:41, 25 May 2011
Line 49:		Line 49:
	*To print a folio, open up the folio in edit or view mode. In the upper right select Renderers > Download PDF rendition. There are also options to create a Zip File of the component documents or an XML rendition of the contents of the folio.		*To print a folio, open up the folio in edit or view mode. In the upper right select Renderers > Download PDF rendition. There are also options to create a Zip File of the component documents or an XML rendition of the contents of the folio.
	*The XML rendition will be of limited use to most Users - it just has information on the metadata of the component documents for the folio.		*The XML rendition will be of limited use to most Users - it just has information on the metadata of the component documents for the folio.

			=Content Basket to Folio=
			*The actions available to a content basket include publishing it to a folio. This does not destroy or empty your content basket. An Advanced Folio will be created.
			*Note that you can also bring that content basket into the Source Items list as you edit an Advanced Folio.

	=Editing Folios=		=Editing Folios=

Stellent at 18:31, 25 May 2011

2011-05-25T18:31:53Z

← Older revision		Revision as of 18:31, 25 May 2011
Line 1:		Line 1:
	=General=		=General=
	*a Folio:		*a Folio:
	**is a container used to hold other documents. It's particularly well suited to sharing groups of documents with other users.		**Is a container used to hold other documents. It's particularly well suited to sharing groups of documents with other users.
	**is a document in ICMS of type Folio		**Is a document in ICMS of type Folio
	**is edited via the ICMS Web interface. Javascript is required.		**Is edited via the ICMS Web interface. Javascript is required.
	**~~can~~ be Locked against further updates		**Can be Locked against further updates
	**~~can~~ be Rendered as PDF, Xml or a zip file		**Can be Rendered as PDF, Xml or a zip file

	*if you look at the actual native file for a folio it's actually XML. The Javascript interface interprets that and gives you a viewing/editing web page.		*If you look at the actual native file for a folio it's actually XML. The Javascript interface interprets that and gives you a viewing/editing web page.

	*It helps to think of a Folio as a real book.		*It helps to think of a Folio as a real book.
Line 44:		Line 44:
	=Folio Templates=		=Folio Templates=
	*ICMS admins need to get involved to make a Folio Template		*ICMS admins need to get involved to make a Folio Template
	*~~available~~ for Advanced Folios only		*Available for Advanced Folios only

	=Generating PDFs from Folios=		=Generating PDFs from Folios=
Line 93:		Line 93:

	==Folios vs Contribution Folders==		==Folios vs Contribution Folders==
	*~~you~~ can make a Contribution Folder yourself		*You can make a Contribution Folder yourself
	*~~supports~~ documents and folders for documents, like an Advanced Folio does.		*Supports documents and folders for documents, like an Advanced Folio does.
	*~~documents~~ in a Contribution Folder inherit a lot of metadata from the Contribution Folder		*Documents in a Contribution Folder inherit a lot of metadata from the Contribution Folder
	*~~both~~ have editing interface which are different from what is typical in ICMS. CFs can work via webdav, so you can drag and drop documents into a folder like any other file operation on your computer.		*Both have editing interface which are different from what is typical in ICMS. CFs can work via webdav, so you can drag and drop documents into a folder like any other file operation on your computer.
	*You can traverse a tree-like structure to see the hierarchy of the folder.		*You can traverse a tree-like structure to see the hierarchy of the folder.
	*Like Folios, you will find that Contribution Folders have complicated and sometimes buggy behavior.		*Like Folios, you will find that Contribution Folders have complicated and sometimes buggy behavior.
Line 106:		Line 106:
	=Known issues with Folios=		=Known issues with Folios=
	*Multiselect Problems		*Multiselect Problems
	**~~one~~ can click on a single item, shift-click to select a series of contiguous items but CANNOT option/command click to select discontiguous items.		**One can click on a single item, shift-click to select a series of contiguous items but CANNOT option/command click to select discontiguous items.
	*Insert Selected Source does not preserve HTML in the title		*Insert Selected Source does not preserve HTML in the title
	*Search window layout is not optimal		*Search window layout is not optimal
Line 112:		Line 112:
	*Document Search Truncates Titles		*Document Search Truncates Titles
	**When searching for Scheduling & Planning Meetings documents and adding to a folio, Barb noticed that the titles were truncated (they have dates at the end which were excluded.) Going to the folio first and searching within that interface worked fine.		**When searching for Scheduling & Planning Meetings documents and adding to a folio, Barb noticed that the titles were truncated (they have dates at the end which were excluded.) Going to the folio first and searching within that interface worked fine.
	*~~new~~ revision causes Folio to get stuck in ArgonneEntry		*New revision causes Folio to get stuck in ArgonneEntry
	**Not sure of the cause, but some folio edits are getting stuck in the ArgonneEntry parent workflow, requiring an admin to approve them through.		**Not sure of the cause, but some folio edits are getting stuck in the ArgonneEntry parent workflow, requiring an admin to approve them through.
	*Browser quirks		*Browser quirks
	**As Folios are largely written in Javascript, a language which runs in the Users computer browser, we have encountered situations where the layout or behavior may be affected by the operating system and browser. It's not an optimal solution but when you encounter a problem with a folio, try to do the same thing from another browser. It's often the shortest past to a solution and frequently the best we can recommend as tech support for this product.		**As Folios are largely written in Javascript, a language which runs in the Users computer browser, we have encountered situations where the layout or behavior may be affected by the operating system and browser. It's not an optimal solution but when you encounter a problem with a folio, try to do the same thing from another browser. It's often the shortest past to a solution and frequently the best we can recommend as tech support for this product.

Stellent: /* General */

2011-05-25T18:29:45Z

General

← Older revision		Revision as of 18:29, 25 May 2011
Line 11:		Line 11:
	*It helps to think of a Folio as a real book.		*It helps to think of a Folio as a real book.
	**It's a grouping of documents, like chapters in a book.		**It's a grouping of documents, like chapters in a book.
	**It is easy to look at all the contents in a folio. You can export a folio to PDF, this combines all the member documents just as a book is a seamless combination of all the chapters		**It is easy to look at a listing of all the documents in a folio, as you would look at a table of contents for a book.
			**It is equally simple to look at the contents of all the documents in a folio. You can export a folio to PDF, this combines all the member documents just as a book is a seamless combination of all the chapters

	=What Document Metadata is Saved in the Folio?=		=What Document Metadata is Saved in the Folio?=

Stellent: /* General */

2011-05-25T18:28:14Z

General

← Older revision		Revision as of 18:28, 25 May 2011
Line 1:		Line 1:
	=General=		=General=
	*a Folio:		*a Folio:
			**is a container used to hold other documents. It's particularly well suited to sharing groups of documents with other users.
	**is a document in ICMS of type Folio		**is a document in ICMS of type Folio
	**is edited via the ICMS Web interface. Javascript is required.		**is edited via the ICMS Web interface. Javascript is required.

Stellent: /* Folios vs Contribution Folders */

2011-05-25T18:27:18Z

Folios vs Contribution Folders

← Older revision		Revision as of 18:27, 25 May 2011
Line 96:		Line 96:
	*both have editing interface which are different from what is typical in ICMS. CFs can work via webdav, so you can drag and drop documents into a folder like any other file operation on your computer.		*both have editing interface which are different from what is typical in ICMS. CFs can work via webdav, so you can drag and drop documents into a folder like any other file operation on your computer.
	*You can traverse a tree-like structure to see the hierarchy of the folder.		*You can traverse a tree-like structure to see the hierarchy of the folder.
			*Like Folios, you will find that Contribution Folders have complicated and sometimes buggy behavior.

	==Folios vs Library Folders==		==Folios vs Library Folders==

Stellent: /* Deciding when to use a Folio */

2011-05-25T18:24:53Z

Deciding when to use a Folio

← Older revision		Revision as of 18:24, 25 May 2011
Line 82:		Line 82:

	As you consider whether your needs are best addressed by a Folio, here are some things to know about some similar objects in ICMS.		As you consider whether your needs are best addressed by a Folio, here are some things to know about some similar objects in ICMS.

			None of the three options below can match the ability of a Folio to generate a PDF/Zip file of all the member documents.

	==Folios vs Related Content==		==Folios vs Related Content==
	*RC is a parent-child relationship that can be nested arbitrarily deep		*RC is a parent-child relationship that can be nested arbitrarily deep
	*RC is just a little bit of metadata attached to each document. There is no 'Related Content' document that is stored in ICMS for a relation		*RC is just a little bit of metadata attached to each document. There is no 'Related Content' document that is stored in ICMS for a relation
	*RC doesn't allow you to print a PDF of all the member documents.
	*There is nothing in ICMS which can give you a tree-like map of all documents which are directly or indirectly related to a document of interest.		*There is nothing in ICMS which can give you a tree-like map of all documents which are directly or indirectly related to a document of interest.

	==Folios vs Contribution Folders==		==Folios vs Contribution Folders==
	*you can make a Contribution Folder yourself		*you can make a Contribution Folder yourself
			*supports documents and folders for documents, like an Advanced Folio does.
	*documents in a Contribution Folder inherit a lot of metadata from the Contribution Folder		*documents in a Contribution Folder inherit a lot of metadata from the Contribution Folder
	*both have editing interface which are different from what is typical in ICMS. CFs can work via webdav, so you can drag and drop documents into a folder like any other file operation on your computer.		*both have editing interface which are different from what is typical in ICMS. CFs can work via webdav, so you can drag and drop documents into a folder like any other file operation on your computer.
			*You can traverse a tree-like structure to see the hierarchy of the folder.

	==Folios vs Library Folders==		==Folios vs Library Folders==
	*ICMS admins need to get involved to make a Library Folder		*ICMS admins need to get involved to make a Library Folder
	*~~always uses the most current revision~~ of ~~any document~~ in the ~~folder~~		*Library folders are integrated tighter into ICMS - if you wish to share a group of documents with all users, this may be a factor. Library folders are accessible on everyones home screen as well as through 'Browse Content > Library Folders' in the web interface.

	=Known issues with Folios=		=Known issues with Folios=

Stellent: /* Folios vs Contribution Folders */

2011-05-25T18:21:31Z

Folios vs Contribution Folders

← Older revision		Revision as of 18:21, 25 May 2011
Line 91:		Line 91:
	==Folios vs Contribution Folders==		==Folios vs Contribution Folders==
	*you can make a Contribution Folder yourself		*you can make a Contribution Folder yourself
	*documents in a Contribution Folder inherit a lot of metadata of the ~~folder itself~~		*documents in a Contribution Folder inherit a lot of metadata from the Contribution Folder
	*~~always uses the most current revision of any document~~ in ~~the~~ folder		*both have editing interface which are different from what is typical in ICMS. CFs can work via webdav, so you can drag and drop documents into a folder like any other file operation on your computer.

	==Folios vs Library Folders==		==Folios vs Library Folders==

Stellent: /* Folios vs Related Content */

2011-05-25T18:18:51Z

Folios vs Related Content

← Older revision		Revision as of 18:18, 25 May 2011
Line 86:		Line 86:
	*RC is a parent-child relationship that can be nested arbitrarily deep		*RC is a parent-child relationship that can be nested arbitrarily deep
	*RC is just a little bit of metadata attached to each document. There is no 'Related Content' document that is stored in ICMS for a relation		*RC is just a little bit of metadata attached to each document. There is no 'Related Content' document that is stored in ICMS for a relation
	*~~always uses~~ the ~~most current revision~~ of ~~any~~ document ~~in the folder~~		*RC doesn't allow you to print a PDF of all the member documents.
			*There is nothing in ICMS which can give you a tree-like map of all documents which are directly or indirectly related to a document of interest.

	==Folios vs Contribution Folders==		==Folios vs Contribution Folders==

Stellent: /* Deciding when to use a Folio */

2011-05-25T18:16:43Z

Deciding when to use a Folio

← Older revision		Revision as of 18:16, 25 May 2011
Line 81:		Line 81:
	=Deciding when to use a Folio=		=Deciding when to use a Folio=

	As you consider whether your needs are best addressed by a Folio, here are some ~~factors~~ to ~~consider with~~ some similar objects in ICMS.		As you consider whether your needs are best addressed by a Folio, here are some things to know about some similar objects in ICMS.

	==Folios vs Related Content==		==Folios vs Related Content==