Rules of Engagement

designpadAI and Robotics

Dec 1, 2013 (3 years and 8 months ago)

95 views



V.3
.1

1/28/2002

ACM/Vendor

Rules of Engagement


The purpose of this document is to outline both the
responsibilities
and the
expectations

that concern each party.



1. File Uploads


When a vendor uploads files, to the
/deposit/pubname/

directory, it is the
responsibility
of the vendor to notify the ACM contact, by email, providing the following
information.




File Name

e.g. doceng01.xml, isss01.xml, csur
-
32
-
3.xml, cell
-
auto.xml



Template Type

e.g. Proceedings, Periodical, Whole Book, Divisible Book



Description of file conte
nts

e.g. Computing Surveys, Vol. 32, Issue 3 (Sept. 2001)



Live data?: Y/N



Original submission?: Y/N



Re
-
submission number:

e.g. 1, 2



Comments

e.g. Thanks for the clarification re: author roles, this information helped us
repair

this particular file.


Exampl
e 1:

From: Sheridan Printing

To: Gerry

Subject: Upload


File Name:

doceng01.xml

Template:

Proceedings

Desc:


Symposium on Document Engineering

Live?


Y

Original?

Y

Re
-
sub?

N

Comments:

Thanx to Craig (re phonecall) letting us know that the 'speaker' of th
e
'keynote' should be identified as an 'author'.


Example 2:

From: MCM

To: Gerry

Subject: Upload


File Name:

cell
-
auto.xml



V.3
.1

1/28/2002

File Type:

Whole Book

Desc:


Cellular Automata…

Live?


Y

Original?

N

Re
-
sub #?

1

Comment:

(From Hong: Sorry the initial file didn't
parse, a typo in the app. code
-

now fixed
-

here it is again.)



2. File Names


The file extensions chosen should reflect the particular format. Since files will be,
predominantly, PDF and/or XML, use ".pdf" and ".xml" respectively. Do not use any
other f
ile extensions


check with your ACM contact if unsure. The actual file
names

should be
intuitive



not cryptic with date/time stamps embedded. We, here at ACM,
have worked with other vendors in the past where cryptic filenames were the norm and
this meth
od proved, in the long run, to be extremely burdensome for all concerned.



3. Method of Transfer


Please be careful when ftp'ing. Remember PDF files are
binary

and, as such,
require
binary

mode during transfer. XML files can be transferred using either
AS
CII

or
binary

mode. So the 'safest' method is to transfer
all

files using
binary

mode or
auto.



4. Method of Submission


One

XML file
per job

should be uploaded. If your particular in
-
house production
method produces a multiplicity of files then these sho
uld be concatenated so as to
produce a
single

XML file. For instance, if there are 4 articles associated with a particular
(journal) issue, then
one

(periodical) XML file should be uploaded consisting (internally)
of four <article_rec>'s.



5. File Integri
ty


All XML files should parse


they should not merely be
well formed
.
Vendors
should parse/check their files
prior

to delivery
. Any files that do not, at a minimum,
parse against their respective DTD will be returned


placed in the vendor's
pickup

area
for repair. The vendor will be notified (by email) that file(s) are being returned and the
reason(s) why.



6. Templates/DTDs


Please use the most up
-
to
-
date template and/or DTD to enter/supply the necessary
metadata to ACM. ACM, in turn, will notify all
vendors if any updates are forthcoming
so that users can download the most recent version.





V.3
.1

1/28/2002

7. Directory (Folder) Structure/Hierarchy/Naming Conventions


In each vendor's ftp area there exists both a
deposit

and a
pickup

directory/folder.
The
deposit

area

is for the upload/storage of files TO ACM and the
pickup

area is where
files, for various reasons, are being returned TO THE VENDOR.


The directory hierarchy


for a typical upload of a Proceedings by, say,
Sheridan, would look, initially, like this:




/
portal_vendors/sheridan/deposit/


The operator, at Sheridan, would create a directory/folder ("pubname") using an intuitive
naming convention e.g. for Document Engineering 2001





/portal_vendors/sheridan/deposit/doceng01/


Within this doceng01 folder ano
ther folder called 'full
text' needs to be created for it is
in
here

that the PDF files should be placed/uploaded.




/portal_vendors
/sheridan/deposit/doceng01/full
text/


The singular XML file, e.g. doceng01.xml should be uploaded to the doceng01 director
y,




/portal_vendors/sheridan/deposit/doceng01/doceng01.xml


Thus, if one were to obtain a 'listing' of the doceng01 directory, only two items should
show up, the
xml file

itself and the
full
text folder

which, itself, contains all the pdfs, e.g.




/port
al_vendors
/sheridan/deposit/doceng01/full
text/p628
-
lin.pdf










… /p662
-
yang.pdf










… /pp694
-
gupta.pdf


8. "Pubname" Directory/Folder

As mentioned, intuitive names should predominate here.



For journals use
journalcode
-
volume
-
issue

e
.g. toms
-
10
-
1.



For proceedings, use
publishedacronymYY

e.g. chi01. If there is no published
acronym, use an
intuitive

short name from the title e.g. doceng99 for the
Proceedings of the 1999 Symposium on Document Engineering
.



For whole books, use
bookDAT
E
, e.g. wholebooks10
-
03
-
01. (Please do not
submit more than one file of wholebooks per day.)



For divisible books, use
divbooks10
-
03
-
01
, if submitting one file per day,
otherwise use
firsteditorlastname
-
firstsignificantwordoftitle


e.g. smith
-
operating

(For

a divisible book, edited by John Smith entitled Operating Systems).


8. "Pubname" Directory/Folder


When a delivery has successfully been processed, scripts will move (not copy) the
associated files/folders from the
deposit

directory over to the
complete
d

directory. In this


V.3
.1

1/28/2002

way the
deposit

directory will act both as a queuing mechanism and a visual indicator as
to whether files are
active
or not.