Pages.UPD: Difference between revisions
From Iskomunidad
| Line 32: | Line 32: | ||
#'''Pages.UPD''' sites are to be generated or maintained by persons with existing formal, institutional UPD affiliation, including faculty, administrative staff, and researchers. | #'''Pages.UPD''' sites are to be generated or maintained by persons with existing formal, institutional UPD affiliation, including faculty, administrative staff, and researchers. | ||
#Information on '''Pages.UPD''' sites is instantly made public. It can be indexed, archived, or rendered persistent by non-UP entities like search engines and content aggregators. It is recommended that internal UP documents be properly created, processed, archived, maintained or shared via an '''internal''' document management system like '''[[UPDox]]''' or via a learning management system like '''[[Uvle|UVLe]]'''. | #Information on '''Pages.UPD''' sites is instantly made public. It can be indexed, archived, or rendered persistent by non-UP entities like search engines and content aggregators. It is recommended that internal UP documents be properly created, processed, archived, maintained or shared via an '''internal''' document management system like '''[[UPDox]]''' or via a learning management system like '''[[Uvle|UVLe]]'''. | ||
#Avoid duplication or having multiple, potentially conflicting or confusing sites. If a UPD unit already has a website, the same unit cannot create a '''Pages.UPD''' site and reproduce the same information. It may, however, use Pages.UPD for its projects or faculty or researchers' profiles that are not available on the original site. If a '''Pages.UPD''' site is meant to supersede an old site, the latter must be deleted or archived in a non-public facility. | #Avoid duplication or having multiple, potentially conflicting or confusing sites. If a UPD unit already has a website, the same unit cannot create a '''Pages.UPD''' site and reproduce the same information. It may, however, use '''Pages.UPD''' for its projects or faculty or researchers' profiles that are not available on the original site. If a '''Pages.UPD''' site is meant to supersede an old site, the latter must be deleted or archived in a non-public facility. | ||
#A site on '''[http://pages.upd.edu.ph Pages.UPD]''' has to have contact information that includes an official UPD email address. | #A site on '''[http://pages.upd.edu.ph Pages.UPD]''' has to have contact information that includes an official UPD email address. | ||
Revision as of 19:41, 5 January 2014
Pages.UPD is an easy-to-use platform for the creation and maintenance of online sites for UPD units and projects as well as for profiles of UPD faculty and researchers. It seeks to fill the gap between well-developed UPD websites and outdated (if not abandoned or non-existent) sites of certain UPD units, projects, faculty and researchers.
Login requires UPD (Faculty) Webmail account.
Features
Based on Openscholar, Pages.UPD features the following:
- instant, template-based publication of scholarly contents, with minimal-to-zero technical know-how required
- built-in content management system
- category tagging for added navigational ease
- built-in site analytics
- social media integration
- drag-and-drop layout
Terms of Use
- The use of the Pages.UPD service shall be consistent with the University's Acceptable Use Policy.
- On Pages.UPD, keep it academic or official. A less formal, more collaborative, community-oriented site like iskWiki may complement a Pages.UPD site.
- Allowed pages include profiles and information on UPD units or their affiliated offices, profiles of UPD faculty and researchers, UPD research or administrative projects.
- Pages.UPD sites are to be generated or maintained by persons with existing formal, institutional UPD affiliation, including faculty, administrative staff, and researchers.
- Information on Pages.UPD sites is instantly made public. It can be indexed, archived, or rendered persistent by non-UP entities like search engines and content aggregators. It is recommended that internal UP documents be properly created, processed, archived, maintained or shared via an internal document management system like UPDox or via a learning management system like UVLe.
- Avoid duplication or having multiple, potentially conflicting or confusing sites. If a UPD unit already has a website, the same unit cannot create a Pages.UPD site and reproduce the same information. It may, however, use Pages.UPD for its projects or faculty or researchers' profiles that are not available on the original site. If a Pages.UPD site is meant to supersede an old site, the latter must be deleted or archived in a non-public facility.
- A site on Pages.UPD has to have contact information that includes an official UPD email address.
Developers
- Jastinne Cesar Macalalad
- Ma. Cristina Dalupan
- Jeffrey Llano
- Althene Faustine Labog
- James Eric De Dios
To Dos
- academic staff authentication
- category-specific themes